I have rotated between countless titles over several decades. What I do hasn’t really changed. Currently I’m not even aware what my official title is and when someone asks I usually say something along the lines of I make IT go but in my native language.
A load of the devs at my original dotnet shop are still there, but are now called stuff like “Vice President Regional Director Lord Protector Master Technical Architect”. I suspect they’re all still writing VB.
I like Computer Programmer. No mistaking it. Developers are people who organise houses to be built. Engineers work on trains. Coders encrypt data. No matter what nonsense word salad it says on my email signature, when I’m at a barbecue I say I’m a computer programmer.
I used to work for Cisco (the huge router etc. company) but my mom thought I was working for Sysco (the food services supply company). She was very surprised to learn that I had anything at all to do with computers.
I usually say “I’m a computer toucher” or “computer programmer” if I don’t want to talk about what I do. If I want to flex some nerd cred, and/or boast a little, I’ll usually say “I work with machine automation” or “robotics”. It tends to get a more curious response and I can talk about some of the weird stuff I’ve helped make.
I would say I’m a fairly proficient dev overall, though on this one project I had to work the frontend. It was shit. Everything was shit.
The backend was a steaming pile of crap, and all of the implications of terrible design decisions were offloaded to the frontend. The frontend became the source of every single delay as it was where all crap started to surface. They were ignoring it, so besides frontend communication was also crap. Eventually, in line with ignoring all other issues, they sacked me.
Long story short, backend devs: treat your FE devs well.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.