I am a programmer
The problem I have with Patrick's essay ("you are not a programmer") is that it addresses a situation that hardly any developer ever finds himself in. If I go to interview for an engineer position, it matters exactly not one bit that I try to pass myself off as a solutions architect or a business problem solver, except for possibly some awkward glances back and forth. All they want to know is how long I've been coding Blub, which frameworks I use and why did I quit my last job? If all is well I will start on Monday with checking out the SVN repo and start getting to know the code. Should I start trying to analyze the company's business processes that would be an awkward conversation indeed with the department manager.<p>I think that is the reality most developers find themselves in. I doubt it's been any different for Patrick until the consultancy spinoffs he can now pull on account of his personal brand.<p>So I kind of agree with Jacques here, with the exception that I don't call myself a programmer in conversation with people outside the field, since it sounds a bit like "punch card operator". That doesn't change the fact that I really am a programmer first and foremost.