-
Website
http://osteele.com -
Original page
http://osteele.com/archives/2008/01/programmers-pyramid -
Subscribe
All Comments -
Community
-
Top Commenters
-
llimllib
1 comment · 2 points
-
sbecker
1 comment · 1 points
-
mattherdy
1 comment · 1 points
-
ultrasaurus
1 comment · 1 points
-
Facebook User
2 comments · 1 points
-
-
Popular Threads
Nice chart, Oliver. Fun way to think about it.
And I notice that "providing commentary on the commentary" doesn't show up in the picture. Quite right.
That saud, I would add, even more code reading, in particular bad code written by others and understanding what is so bad about it, and why is it bad.
Reading your own code is not so effective: you already know what it does and, even worse, you'll always think it's good code.
Getting feedback on your code is important if you can. Ask people for reviews if you can (and shut your mouth). Look at how other people changed the code you wrote. Did they rewrite it instead? Are they using your libraries effectively?
Reading blogs can be misleading, anyone can write on blogs, even bad programmers: read them, but with a reserve.
I hope this didn't sound polemic, I'm just trying to refine the original message in the post.
I can't be the only one who wakes up the morning with a solution that I apparently coded in my sleep?