Career Advice: Don't Call Yourself a Programmer 422
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 ... (Score:5, Funny)
Re:Makes sense (Score:3, Funny)
I knew AD&D would help! (Score:5, Funny)
That's why I put "20th Level Code Rogue/Network Warlock" on my resume.
Re:Makes sense (Score:5, Funny)
Are you saying you are the 1%?
Re:more fun.. (Score:3, Funny)
Hi! I'm the Versatile Administrator of Giant Interconnected Network Architectures, nice to meet you.
It's not firing (Score:4, Funny)
No, it's called a divorce :P