Codecraft
technically.us
technically.us
I can't say that I see that in my daily life at all. Usually, when I'm around non-technical people, if I mention what I do at my job, or what some of friends do at theirs, most people are interested, and want to hear more.
Perhaps this is just an artifact of living in the Bay Area. Do others hear this same sentiment?
That being said, I think this article is right on about considering programming a craft, and is very well said.
Seriously, one thing that people outside computing really appreciate about our job is how fast things change. For the average person over 35, it feels like everything about their job changed in the last twenty years, even the last ten years, and it will keep changing for another ten years. It's scary and challenging, and sometimes they're afraid they won't keep up. And for the average person, it was all driven by computers, directly or indirectly. So they look at me and realize they're exaggerating; compared to my job, their job has only changed a little bit. But the change doesn't faze me a bit. For the average person under 35, they're thrilled with how fast things are changing, and computer guys are the ones who understand it and make it happen. (We probably get more credit than we should. Scientists and engineers have fallen too far from their "Masters of the Future" position in the public eye; they should be right up there with us.)
I think there's a crucial bit of context missing here. I live in Chile and I can tell you that most (but not all) of the places at which I've worked treat programmers as second-class employees.
Here are some extreme perceptions I've witnessed at some of my jobs: we are either incompetent or overpaid; we have to be monitored and managed correctly, otherwise we'll slack away and/or engage in miscellaneous mischief; we never get things done on time, within the budget or the way the users want them; in other words, we're just a sinkhole for money.
On the other hand, if you talk to a non-technical person outside the workplace context, they'll usually react the way you describe it. I think that, in the end, it all depends on the culture, both corporate and general.