Re:Ask HN: How can I self-evaluate my programming skills?
by pavelkaroukin on Friday January 06, 2012 @02:21PM
(#3434624)
Never stop coding. Look back each 3/6/12 months at code you wrote back then. If it looks as cool as it was 3/6/12 months ago - you stuck. If it looks like shit - you are on a right track and right speed.
[ Parent
| on HN ]
Re:Ask HN: How can I self-evaluate my programming skills?
by carucez on Friday January 06, 2012 @02:33PM
(#3434671)
Occasionally, I take 2-4wk coding breaks to re-evaluate something that's been nagging me each time I code. Is OO working for me? Do I like functional languages (I don't)? How's that PHP treating you (unstable buggy broken)?
I've discovered that PHP makes me angry. Functional is good for small stuff. I need [much] more practice with OO. I don't know anything about ... a lot.
The next 2-4 wks are spent reading and comparing alternatives to doing whatever it was that was nagging me. These time blocks do actually include small coding problems (1-2hrs), but I can't really call it coding. I then begin with new optimism about the new language/skill/feature/paradigm that I've now incorporated into my daily programming.
Re:Ask HN: How can I self-evaluate my programming skills?
by pavelkaroukin on Saturday January 07, 2012 @01:06PM
(#3437585)
Offtopic, but since I see you lean more toward OO - look into perl's Moose. There are few presentation on Moose basics out there. Especially, look for Roles/Traits.