Explaining my job is trivial compared to the insanity I cook up in my spare time.
Oh, so you like gaming? No, I’m actually not playing the game. I’m building a mod for it. Erm, okay, so this is for other players then? No, I’m mostly building it for myself. Ah, so you haven’t put a lot of time into it yet? Roughly 12 years. What? So what does the mod do then? It plays the game for me, and publishes in-game metrics to a monitoring application, so that I can see the progress of the game in an abstract form while I’m on the couch, thinking about how to optimize the automation further.
Regular fun stuff.
Yes, I do. I’m a devops engineer and even “coding camp devs” have problems understanding what I do for a living.
I think most devs even only have worked in software companies that sell software where devops isn’t as critical and complex since there’s not “production” environments. When you work for a company who makes software for themselves and/or hosts software from other companies themselves, devops is a much bigger deal. Even moreso if it’s a heavily regulated industry like healthcare. Most other companies don’t spend much on devops or even often make the developers do that work themselves.
Yeah, I work in cyber forensics where everything I do is confidential, so yeah, I can’t actually explain my job which makes it difficult to explain my job
Depends on wether I want them to understand. If I just say we are the ISP for universities and other schools of higher education then they mostly go, “Ah okay”, but it seems like no one has any idea what that means. I feel like despite using them daily people don’t even know what a network is sometimes.