This is very similar to the rants I've given and heard from plenty fellow students back when I was still studying a few years ago. I can see exactly where it's coming from, and yet I can't agree. Partly it's the blatant snobbery of it, which I know from my own experience. It's frustrating to see folk with no interest in the discipline do better because they're more focussed on getting a first than actually learning anything.<p>The thing is, the industry is a lot bigger than it seems when you're at university. Developers/programmers are actually a pretty small part of it. For example, software testing/validation is a job in itself which can involve very little coding. Professional documenters are paid to write about software and do very little coding, but an understanding of the field is still useful to them. And lets not forget the good old ranks of management, forever considered to be a complete waste of time that gets in the way of "just hacking shit out". Except it turns out people don't want shit.<p>So basically, just because somebody is on your course and doesn't want to spend all night fiddling with their ubuntu installation, reading HN and learning the stuff you know that you'll need for the job you want, doesn't mean they wont be able to hack it in industry. If anything the industry could do with more normal people. Preferably ones with boobs.
I'm not sure this essay has much value. There are some fairly obvious observations, like "learning takes work", "not everyone is good for every career", "learn from your mistakes", and "programming involves typing". That's fine, but not particularly insightful.<p>Perhaps less useful is the author extrapolating from his community college classmates to the general programmer population.<p>But the part I disagree with is the reductionist description of programmers as people who only type and solve problems. This is only true if you expand the definition of "problem" to be so broad that it's meaningless. As a good software developer, you have to make aesthetic choices, exhibit empathy with customers and coworkers, do boring paperwork, be personable, and many other things. I'm not sure all of these things are problem solving.<p>I also don't think any of his 8 pithy statements of advice are very helpful. Just one example: "Take everything very seriously." Really? Is this tongue-in-cheek? How about, "Don't take yourself so seriously. Have fun and be curious about your world." That sounds like better advice to potential programmers to me.
This should be required reading for those entering CS programs and, more importantly, for those that want to be developers that have a non-CS degree. There are way too many 'I got a B.A. in Art History but now I need to eat, so I'll program' people in this industry, and it shows.
Site isn't responding for me.<p>Google cache:
<a href="http://74.125.93.132/search?q=cache:jnMtyv9i7LUJ:www.worthlessgenius.com/2009/04/22/so-you-want-to-be-a-programmer/+http://www.worthlessgenius.com/2009/04/22/so-you-want-to-be-a-programmer/&cd=1&hl=en&ct=clnk&gl=us&client=firefox-a" rel="nofollow">http://74.125.93.132/search?q=cache:jnMtyv9i7LUJ:www.worthle...</a>