4 ms·
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
by decode 17y ago
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.
Perhaps less useful is the author extrapolating from his community college classmates to the general programmer population.
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.
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.
- worthlessgenius 17y agoYou do make very good points, and I can't disagree with you. The article wasn't meant to be a blanket statement involving all programmers. It was rather meant to be a rant about how a lot of people who begin to go down that path either don't know what they're getting themselves into, or just simply don't care what kind of burden they are putting on others. As for the statements of advice, you are correct. They are indeed broad, and would do with a good bit of expansion. This wasn't meant to be the alpha and omega of posts about what it means to be a programmer.