Also, sacrificing an hour of productive coding by reading good literature increases the chances that you won't grow up to be a dumb fuck.
Steve's articles may not be of much artistic value, but he combines non-fiction with fiction in a wonderful way, explaining his reasoning through plots and drama :) He gets personal, not being afraid to expose his feelings, and I really wish more people would do that.
My concern isn't invalid. Others have also noticed:
Paul Graham: http://paulgraham.com/selfindulgence.html
Another good article: http://fitnr.com/filtering-the-web-of-noise/
Don't misunderstand, I <3 Yegge and am glad he's back. His writing taught me stuff that should have been covered in my undergraduate education, and I still refer new programmers to his 'Tour de Babel' essay.
But am I alone in wishing writers would cut to the chase a little more so as to help their readers reduce the info overload and the task of filtering through it quickly?
It's not hard to spend an entire day reading through only the high-quality tech blogs alone, and find, as Paul mentioned, that you did a lot of 'fake work' and very little real work.
Steve's stuff is lengthy -- but it's also not posted incredibly often (he's not a career blogger), and I have yet to read much by him that wasn't intellectually or creatively satisfying, and afaict that's rather rare for tech-bloggers.
[0] http://www.amazon.com/gp/product/1934356336?ie=UTF8&tag=...
(Nice affiliate link, but hey I'd do the same)
Is anyone else as torn about long blog posts as I am? On the one hand, I do appreciate good software writing. But I also appreciate concise expressivity, saying more with less. They shouldn't be, and aren't, mutually exclusive.
These days I feel like I'm forced to choose between sacrificing an hour of productive coding to read through a bunch of overly long blog posts at HN and proggit and evaluate whether they were worth reading or not.