+1. This is what I always do too.

I do understand why people avoid "programmer", since it sounds low on the org chart, but replacing it with "senior architectural web consultant" is bad, and suggests that you're embarrassed to be someone who writes code. "Software Developer" is alright, but we're adding letters and a a space between words, and I don't really see why.

Sometimes I think that changing a name over and over shows a bit of insecurity. You know, how lawyers like to introduce themselves as "civil rights lawyers" when in fact they are essentially personal injuries lawyers.

Programmer goes way back. It's a great word, let's use it.

It's good enough for Professor Knuth, Peter Norvig and the other guys of "Coders at work". I reckon it's too good for me and you :)

That's what I say too unless I'm in a techie environment in which case I qualify it with "web programmer". Anything more usually sounds pretentious and at the end of the day your title really only matters when you're talking to management about a raise. If your official title is programmer you're getting squat but if your title is Senior Lead Software Architecture Analyst or something like that you'll get a lot.