Career Advice: Don't Call Yourself a Programmer
Ian Lamont writes "Patrick McKenzie has written about the do's and don't's of working as a software engineer, and some solid (and often amusing) advice on how to get ahead. One of the first pieces of advice: 'Don't call yourself a programmer: "Programmer" sounds like "anomalously high-cost peon who types some mumbo-jumbo into some other mumbo-jumbo." If you call yourself a programmer, someone is already working on a way to get you fired.' Although he runs his own company, he is a cold realist about the possibilities for new college grads in the startup world: 'The high-percentage outcome is you work really hard for the next couple of years, fail ingloriously, and then be jobless and looking to get into another startup.'"
I'm self employed, and even though my boss is jerk he's not going to fire me because I call myself a programmer.
In casual conversation among people who wouldn't know the nuances of the various "programmer"-like terms, I do say, "I'm a programmer." It gets the point across simply that most people understand.
If I'm in a semi-professional setting of white collar adults, I usually say "software developer."
On a resume or among those who know the industry standard, I say "I'm a software engineer" because that's my title.
If it's tied to a conversation that might have career potential, I give the true classification at work: senior software engineer.
Because, you know, the 1000+ currently open job postings for keyword "programmer" on Monster.com are just a perfect example of situations where people are already looking to fire you. After all, that's why they created the posting, just so they could waste company resources and fire someone.
/sarcasm
I do not respond to cowards. Especially anonymous ones.
In Canada, it's illegal to practice engineering, or call yourself one, without a engineers license. There's nothing worse than retards who get a college degree in programming and start calling themselves "engineers". It's an insult to every actual certified engineer in the world.
. . . and 'real' engineers everywhere weep. Obviously every case may be unique, but calling yourself one thing which has a set of implications does sort of slander professionals in the field whose titles you are trying to snag.
That's why I put "20th Level Code Rogue/Network Warlock" on my resume.
If you were me, you'd be good lookin'. - six string samurai
Programming seems easy to you and me, but you would be surprised at how many people just cannot do it no matter how much training you give them. Anyone can clean, most people can do construction. Maybe 1 in 10 people could program if they really wanted to, and only 1 in 10 of those will actually want to.
Are you saying you are the 1%?
Exactly ; they've done studies that prove this - not everyone can program a computer. Every time I see one of those GUI programming environments designed to enable users to program, I sigh. Real programmers detest them (unless they are a mile-high model overview and they fill in the gaps), and people who can't program still can't program, so implementing them is pointless and counter-productive.
If 30-60% of people who self-selected to go on a Computer Science course can't program, what's the percentage in the general population?
Programming seems easy to you and me, but you would be surprised at how many people just cannot do it no matter how much training you give them.
Please mod parent up. This is exactly right. All of my experience, both in school and now working as a software developer, confirms this.
Well, filling in a bunch of formulas IS a form of dataflow programming.
It is easy for non-programmers because it quite closely maps real-world calculations on a sheet of paper to the computer screen - just fill in the initial values and write down formulas without worrying about operations ordering. VisiCalc and those who polished the concept after them did a pretty nice job.
On a side note, Visicalc authors' notes make for quite an interesting read.
I'm a programmer. I have been for over 25 years.
I'm not going to jump on the bandwagon of "software engineer". I think it's as ludicrous as "sanitation engineering."
Any employer who thinks "programmer" is a derogatory or lesser term is too blinded by buzzwords for me to be happy working for them anyhow.
I do not fail; I succeed at finding out what does not work.