Shambling Towards Perfection

Obligatory Shakespeare reference: What's in a name? That which we call a rose By any other name would smell as sweet. Software engineer, software developer, programmer, programmer analyst, systems analyst, code monkey... I always find it frustrating that there are so many different job titles for more or less the same thing. And that's not even getting into specialties (and sub-specialties!) like web, embedded systems, mobile, front-end, back-end etc. etc. If pressed I would say I consider myself a software engineer because of the sheer amount of studying I've done/am doing including that whole 4.0 on a masters degree thing, plus the wide variety of tasks I'm both capable of and currently responsible for (despite the school of thought that says nobody can be called "engineer" unless they've taken a professional engineer exam; the exam in question was discontinued due to lack of interest, so... ). Anyway that's what I put on my LinkedIn. But NMSU ...

This is one of those things that I never gave a second thought to. Growing up in New Mexico, there were more tech jobs in government than in any other industry. White Sands Missile Range, Sandia and Los Alamos National Laboratories, not to mention state, county, and city jobs. My dad plus many of my friends' parents worked in tech for the feds. While there are more and more tech companies moving in, government is still a major player in the area and probably always will be. But that was just my experience. In many areas the tech industry itself is much more prominent, and of course those jobs are the ones that get all the press. You rarely see articles about working as a software developer at the IRS, or something like that. It's always Google or Amazon, a start-up, etc. To many people, being a software developer is synonymous with working in the tech industry. So when Jenny Chan, who founded the Women in Web Dev community, contacted me to ask if I'd do an interview fo...