[...] The Programmer’s Food Pyramid at Oliver Steele (tags: programming software pyramid) [...]

[...] The Programmer’s Food Pyramid at Oliver Steele (tags: programming software pyramid) [...]

[...] Recently, I stumbled across Oliver Steele’s site and found his link to The Programmer’s Food Pyramid. Looking it over, I recognized the importance of most of the items there. Reading code, and reading about code of course. Writing code, how obvious. Revising code, okay, I had always lumped that one into the reading code and writing code blocks, but I could see how it could be considered a separate activity. Then, up there at the top, the one that made me think for a minute. [...]

[...] [CODE] The Programmer’s Food Pyramid, osteele.com, via:labnotes.org [...]

IMHO the size of "Reading Environmental Code" is way below what it should be. Reading your code or well written framework code goes smoothly. Reading "Environmental" code takes a LOT of time trying to figure out the twisted implementation (Have a look a the daily WTF site ;-)..

[...] http://osteele.com/archives/2008/01/programmers-pyramid [...]

I heard people interpreting this pyramid as the learning path of a programmer. An important thing to state here is that it does not represent a learning path (which would have been much more complex), but just the amount of time spent on each activity. Actually I think the food pyramid itself is not very intuitive. I would prefer a pie chart.
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.

[...] The Programmer’s Food Pyramid at Oliver Steele The Programmer’s Food Pyramid at Oliver Steele [...]

[...] The programmer’s food pyramid. [...]

[...] [...]

[...] [...]

[...] ((A take on the more serious Programmer’s pyramid)) [...]

[...] The Programmer’s Food Pyramid at Oliver Steele (tags: code programming) [...]

[...] Оливер Стил представляет версию пирамиды Маслова для программистов, The Programmer’s Food Pyramid at Oliver Steele [...]

And what about "writing about writing about code"?

[...] The Programmers Food Pyramid [...]

Well lamer... if it's by analogy to the Food Pyramid, then it's showing quantity more than relationship. And reading about something is good, but practice is probably more important.

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.

[...] Oliver Steele posted an excellent image in his blog today titled “The Programmer’s Food Pyramid”. I love how the code reading activities form the base of the pyramid. The multitude of high quality open-source projects, coupled with new web apps like Krugle and Google’s code search to index them, finding and browsing quality source code is easier than ever. It’s a great way to pick up new tricks and find out how your peers in the community are solving problems. [...]

[...] The Programmer’s Food Pyramid Great illustration on how a programmer should spend time (tags: programming) These icons link to social bookmarking sites where readers can share and discover new web pages. [...]

I should think "reading about code" would be the bottom of it all eh?