in reply to What do you call yourself?
Being in corporate-land, I get the bizarrely meaningless title of "Systems Analyst." (update - the full title is actually "Systems Analyst - Business Solutions"). I'm not entirely sure what a Systems Analyst means, but in my case it consists of not quite equal parts of:
- functional design of software
- database design
- coding and debugging
- end-user support
- systems administration
- something akin to what they called "evangelism" in the late 90's
My business card and resume say "Systems Analyst" because I feel like that's the honest thing to do. Plus it's a lovely setup for a potential future interview question.
By the way, since I work for a company that manufactures large and complex machines, there's no danger of people calling me an Engineer. Which is fine by me.
Update: I found out that the above is only true because I work in an IT division. The developers who write code for the company's software-related products are called Software Engineers.