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.'"

But ...

[WrongSizeGlass]

I'm self employed, and even though my boss is jerk he's not going to fire me because I call myself a programmer.

Re:Makes sense

[SharkLaser]

Well, programming practically is the computer-world equivalent of construction worker or cleaners. Sure, it's useful so people actually can get things done, but it isn't practically challenging or something lots of people can't do if given teaching. Developers have to make the important decisions regarding a product. If you wanted to work in the gaming industry, would you rather want to be a coder or actually the game designer?

I knew AD&D would help!

[Rinikusu]

That's why I put "20th Level Code Rogue/Network Warlock" on my resume.

Re:Makes sense

[Lemmy Caution]

Are you saying you are the 1%?

Re:more fun..

[neokushan]

Hi! I'm the Versatile Administrator of Giant Interconnected Network Architectures, nice to meet you.

It's not firing

[ryzvonusef]

No, it's called a divorce :P