A friend and I were discussing recently the interesting phenomenon where despite us having highly unrelated jobs/passions with unrelated skillsets, we are both considered “software engineers” because we happen to write code. I believe this happens because when, say, family asks what we do, it usually feels like they’re mainly interested in the day-to-day as opposed to the core purpose of the work. This makes perfect sense and is fine, but between two people who write code it is probably reductive communication.
This prompted us to strip back the code-writing part and come up with a new job title for each of our occupations; my actual job, and his primary interest. The new titles were far more descriptive of the core work we both do that is probably more salient on a fundamental level than the programming part.
Mine was “software engineer” -> “video compression researcher” His was “software engineer” -> “web platform designer/developer” (using developer in the name still feels like cheating, but we couldn’t think of anything else)
SWEs (or CS students): Do this for yourselves. What does this look like for you?
giving rocks anxiety
Digital psychoacousticiamusicolograpist
That’s actually my thing I’m working towards but
I was with you until the last 6 letters…
Nuh uh, its grapist 👉👈
Uh feel yah
Bachelor of Bitical Arts.
I wanted to be an archeologist.
Not only did I fail at my dreams I gave them up for the lie of “job security”.
To be honest software development and archaeology have a lot in common.
Lead googler
Music artist
Professional Emailer
Virtual Lego Assembler; the Virtual Legos are Libraries / PaaS APIs
senior headpalmer
my title is ‘analyst programmer’ so just analyst I guess,
porn star; that is if i were hot. lol
Software Diagnosticist, maybe?
My main role lately has been to jump into failing projects and put them back on track, then leave it back with its own team. Sometimes I’m debugging software, other times I’m “debugging” processes or even team structures. Occasionally even the whole idea behind some project is just messed up and nobody realized.
That sounds pretty cool, I could imagine myself doing that.
How did you get into such a role? Is it some kind of consultancy?
It happened by chance the first few times. Projects were failing and management wanted more resources, I was assigned and noticed problems that hadn’t been noticed. After a few different projects with different issues, I became the default guy to call into ongoing projects. At the time I had already rejected a few promotions because I didn’t like any of the other roles above my position, so I eventually asked management to create a new role for me based on that.
Id just grow chilis and make hot sauce. Probably switch to arch and find an open source project to contribute to for scratching the tech itch.
project manager
i was systems engineer/head programmer and thought i was lucky getting paid for my pastime. 30+ years later i realised i was not lucky at all. so i quit and today i am a fish monger and it feels great. i know, not an answer for your question…