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.
factorio?
Kittensgame
Yep.
Network engineer here. I can't count the number of times my mom says I'm in programming.
After a few years, my wife figured out the best way to describe my job. Doctor of the internet. This was because I was working in operations at the time and would fix network outages regularly.
Did you put an SR to get thru her (mom's) firewall first?
I don't have trouble explaining. I keep it high level and generic because 99 times out of 100, people are just making small talk and want to know just enough about you to categorize you.
Similar with trying to explain the Fediverse. It doesn't come up often, but the explanation is sometimes just
Non-profit run social media
While not entirely accurate since you can run an instance for profit, it's been the case for pretty much every instance and it's definitely true for the side I'm helping with
“I’m a stand-up comic.”
“Ooh! Heckle me!”
“I don’t know anything about you and don’t wanna say anything mean about you. Just enjoy the moment without getting a performer to do free work for you.”
“You’re no fun.”
“Don’t have to be on all the time, let me eat my burger.”
I imagine you get these questions all the time, but how did you get into stand-up, and how did you get the guts to get up on a stage and try to be funny?
I love the idea of stand-up comedy, but I've been to a few open mic nights and it almost always seems like drunk people showing off, people that are hilariously unfunny, or people in the crowd that try to shit on anyone remotely trying to entertain.
I started out as a quizmaster, telling quiz for a night a week. I’d open my show with a new 45-second bit each week, built audience numbers over time.
Then I realized I’d been doing this for years, and was an incredibly prolific comic! I had enough material I could just walk out onto a stage and just lengthen out my opening bits, cause I no longer had a quiz to tell that night!
Reading the first several posts... Is everyone here in IT? 🤣🤣
Mostly, yeah
Given you are using niche forum software. Yes, most likely.
There are DONZENS of us!
No, but only because we subdivide what layman think of as IT into many specialties
Describing my job? Yeah, sure. I do science.
Explaining my job? Hell no. Nobody is willing to read a 20 page lit review to start to understand the background of what I do
Contramuffin. (2024). Describing my job: I do science. Lemmy World, 78(9), 69-420.
I cast spells that make the runes etched in sand translate the energy of magic stones into dancing light.
Usually I just tell people that I work in IT and leave it at that.
"Hey so does that mean you can fix my laptop and make my next gen app idea for free?"
Of course!
Me: I'm in IT (trying to keep it simple)
Them: OK, but what do you do in IT?
Me: I'm a system administrator (again trying to keep it simple)
Them: I don't know what that means. What does a system administrator do?
Me: I work on servers (again, trying to keep it simple)
Them: What's a server?
Me: I'm in IT...
That's a combination of too simple/short in your sentences, mixed with too specific jargon with no clarification. It's dumb as hell that people don't know stuff like what a server is, but if they don't you have to abstract it more.
My go to is some form of: I'm in IT, I do systems administration. I help keep all the things behind the scenes working so that everyone's stuff works at my workplace. Less of making your email work, more of making everyone's email work.
Obviously I work with a hell of a lot more than just email. I'm mostly scripting out custom automation jobs to bridge gaps in the integrations between different systems. But like you said, keep it simple.
Oh hello fellow email admin. What platform?
So you keep the computer engine running.
Replied elsewhere: I cast spells that make the runes etched in sand translate the energy of magic stones into dancing light.
Usually I just tell people that I work in IT and leave it at that.
I'm in DevOps, so anyone not in tech has no idea what I do/what that means. So, I end up just saying "I work in IT".
My new doctor didn't like that answer when we were making small talk and wanted a more detailed answer, so I tell him. He looks at his nurse and says: did any of that make sense?
Huh, I came to say pretty much the same thing. I’m DevOps, more or less, by I tell people I’m a programmer since that’s what I do
I recently told a seven year old that I am a wizard. I already have the beard and being a programmer, that is exactly what my customers feel about my work.
Trouble as in I'm in trouble if I do. I'm a formally educated it security engineer running my own incorporated software and infrastructure company. Firstly: people just hear "computer guy" and their second thought is "he can fix my stuff". So I stay near to the truth and simplify it: I'm a theoretical electrical engineer. Boom, instant bored face and they leave as fast as they can. My neighbors love me, but I haven't fixed a single of their computers in decades.
Also pro tip: the wife has the same qualifications as I, so she fixes her family's stuff herself. My job is to lug stuff and the kids around at home.
simplify it: I'm a theoretical electrical engineer.
So, IT is just theoretical electricity.
I need to remember that 😁
A concept of electrical engineering
Yes. I'm a near surface geophysicist. So I don't look for oil or minerals but I do try to figure out what's going on underground without digging. Mostly looking for mine or karst voids under new construction.
I'm a florist. People understand what I do, they usually just don't think it's worth doing or paying me for my labor.
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.
Nope. I keep the internet working.
People seem happy when I say that. Unless my internet at home craps out and my wife makes a cheeky joke about it.
I'm a software developer. My default explanation to people who don't know what that means is, "I whisper to computers, and sometimes they do what I ask".
My experience is that it almost always does what I ask. The problem is that some times I don't ask it to do what I want it to do in the exact way it will understand.
"Stop doing what I told you to do and start doing what I want you to do!" has been uttered in my office a few times.
As DevOps , I whisper to a room full of computers to do what you told them plus do what some others tell you to break what you did, then run a big hammer over it, and hand all the pieces back to you
Information Security is so hard to explain to old people who don’t know much about technology. My grandparents back then (late 2000s) never understood it no matter how I explained it, and they thought I was a security guard at the bank I worked at. You could also see the disappointment in their faces thinking how someone who took IT in college ended up as a security guard.
Yeah but developed a quick explanation for it: Industrial water treatment tech for HVAC. You know how having a swimming pool or hot tub requires some chemistry? I do that for water in boilers and cooling towers used to heat or cool big buildings
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.
When I say I’m a school librarian, most people can make a connection and have an understanding. And as long as their next comment isn’t some Fox News bullshit (which was real fun at my grandmother’s funeral), I can usually leave it at that.
But the actual day-to-day complexities of what I do isn’t going to be understood. Most days I am checking out over 400 books to students, which means my volunteers, me, and my para (assistant) are checking in and reshelving over 400 books each morning. That’s over 800 books scanned each day. Then, I am also teaching six 45-minute classes every day and I see each student in our school (over 700) twice a week in those classes. So I am planning and prepping for those classes, teaching those classes, and running the book checkout. Not to mention managing behaviors and helping some of our new students (especially kindergarten) understand the expectations of the library. I am currently planning our book fair happening in a few weeks, getting ready to start my after school club, facilitating a $500 per grade level order for books and supplies, fielding sales phone calls, balancing my ~$10K budget, and being the team lead which involves monthly meetings to attend, twice a month meetings to run, and many additional emails. So yes, I do read to kids and let them take books home, but that’s nowhere near the end of my to-do list.
I am a clerk in a bakery.
I mostly put bread in bags, and those bags on shelves.
Yep. Sometimes I can't even figure out what they pay me for.
Kind of. I am a CEO (that's the easy part) of a small consulting company in healthcare.
The hard part is to explain what we actually do: We do consult organisations about (healthcare related) disaster preparedness/risk management and contingency planning. So you call us if you want to have proper plans in case your hospital catches fire, COVID and monkey pox have baby or if you are a city and need to know how to plan for "the day X". But as we work mainly on a systemic level you can also call us if you need a more intelligence focused plan e.g. "I am going to South Sudan, what do I do if I have an accident?".
Additionally we also consult for ambulance services, e.g. how to plan vehicle allocation, etc.
Mine is usually pretty simple to explain. I do CNC, which is cutting objecting/materials into useful shapes using big machines.
Guess my job based on the following description:
I sell a product to a people who don't believe they have any use for it during what they consider their personal time.
Answer:
Tap for spoiler
I am a middle school math teacher.
Game Dev here. More specifically, audio director. Used to be tech sound designer and composer. I find it hard to explain even over here, among the geeks like me.
My job title is an acronym, inside the company no one seems to agree on what this acronym stands for. So yes, I just say I work in the Automotive industry.
Ya I'm still lying about being laid off almost 2 years ago, so it's kinda rough
What did you do?
I was a front end dev. I am just coasting on depression and savings until I figure out what I wanna do.
It's hard to explain a job where I watch YouTube most of the time, and then I do random when I am asked to do some stuff.
I'm a public servant, so while it's easy to tell people I work for The Government, it's a lot harder to explain what I do. My job is a mish-mash of like three different roles in one of the least popular departments. When people ask, I say I work for (our version of) the DMV, and that's usually good enough.
No.
My friend had this problem, I knew him for a while and couldn't figure it out. I believe he was a "Transpondster".
That's MISS Chanandler Bong.
Automation for mainly the mining industry.
Depends on their level of interest and/or knowledge. My job isn't exciting or prestigious, just niche/specialized. Most of the time when I say what I do, I get a blank stare. If that's the case I'll just say "I babysit computers" and leave it at that. I've had the conversation enough times that I know it's not worth the effort to try explaining it further. "Oh, you work with computers? My brother in law is a programmer, perhaps you've met him?"
Sometimes people will get the gist of it just from the title, and these are usually the most interesting conversations because they've made the (un?)conscious effort to understand something new to them. I am totally down with that.
On very rare occasions someone will actually know what it is that I do. This inevitably leads to trading war stories about redundant alerts to please management, unbalanced power loads, poorly defined environments handed over with little to no explanation, cable curtains, and how even other IT people have no clue what we're on about half the time.
those who know dot jpeg
I juggled datacenter design/management/maintenance, infrastructure, and enterprise monitoring, but only one of those was tied to my "Senior Engineer" title. The rest were just things that ended up as my job because I was good at them. So my resume looks like I'm lying through my teeth. Thanks, aversion to change!
Shout out to any other Solarwinds Orion admins who got that mess duct taped to their position. Drinking game idea: take a shot for every 100 nodes being managed. Or don't, if it'll lead to alcohol poisoning. 😒
Solarwinds Orion
We don't curse in this household.
Anyway, guessing it's the classic "sales sold the demo of a perfectly configured setup maintained by a dedicated team, management expects you to make that happen alone on top of everything else you already do" situation? Multiple years into cleaning up the mess of that shit at my place.
Hello fellow sufferer.
Not quite the same on my end but it ended up in the same place. When I started there were already two instances running (one for the parent company and one at my location, which had gotten acquired). Maybe a hundred nodes all together, and our job was just responding to alerts in a mostly out of the box setup. Then my boss got sick of trying to work around limitations of that setup and demanded admin access so our team could at least make adjustments. Which eventually turned into me being asked to add nodes, which turned into me being the primary administrator. Which was actually pretty sweet for a bit because I got to learn a lot, both about the software and the company. Finally convinced management to merge the two installations rather than rely on that EOC garbage.
Then the acquisitions started rolling in.
By the time I walked out there were 2000+ nodes in a dozen locations, and it was still just me and somehow still just a side job.
Orion has its faults but after migrating so many acquisitions from a handful of other platforms I still prefer it. Everything seems like it's optimized for small installations and/or specific platforms. When shit gets that big you need a team to run it properly. Which is why I'm allowed to say "Solarwinds" in my house, but guests are asked to leave if they mention the C-suite as anything but sociopathic leeches.
I'm working on making robots do useful things. I think that's fairly easy for most people to understand.
I don't have a job, so no trouble at all.
Nope, most people are fine with "I'm a programmer", the few times someone asked me what exactly did I program, I answered with the ELI5 version of what I do and that's always been enough, e.g.
- I make computers see and understand what they're seeing.
- You now site X? I work there
- You know game X? I work in the servers for it
No. I do not.
Nah, like 50% of it is just telling people to restart their computers.
Yes, definitely. It's easier now that I'm part of operational support and can oversimplify it by referring to myself as an IT dude, but back when I was part of the field rotation, when I tried to sum up what "offshore seismic survey technician" is, I was sometimes asked "so, how's it like working on an oil rig?".
I wouldn't know, I've never been on one. I've been on ships around them, but never on the rigs themselves.yes and no.
I work as an it support in a small software company, so i do lots of stuff:
data integration / migration, fixes in our legacy products & websites, and of course fixing printers.thats way to complicated explain in detail,
but just saying IT support doesn't do it justice (people just think im the guy that tells people to "turn it of and on again" if i leave it at that)Instead of telling people directly what i do,
i just tell them i work in IT, this is what my company does, and i work on these products.i have problems explaining my job to myself. As I sit on the floor, painting a wall or scrubbing the floor or as I'm trying to repair a door... yeah that's not my job description
Not really. I tell them it's like a Black Mirror episode and they give me a sympathetic grimace. Then we talk about something else.
Ugh, why did I immediately jump to working with pigs? I'm still scarred.
I have two ways of explaining. The first one is just saying “I work with data” followed by some hand waving and shrugging.
The other is where I really go into detail and explain everything. Going gaga over some minute aspect that I find awesome but couldn’t even interest one of my coworkers.
Neither seems to really work, but I don’t get follow up questions which suits me just fine :)Yes, if they are really interested and don't have IT background. My mother once thought I look up codes in books and type it into the computer.
Someone needs to tell her about Stack Overflow.
yes
No.
"I keep the computer systems running at the local newspaper, and prevent it from getting hacked" is pretty straightforward.
It provides enough to latch on to for normie small talk.
And I can dose the tech talk based on what questions I get back.So you're the one who changed the password from admin/admin to admin/hunter2? That's all I needed.
I changed the password to a 256 character string, disabled pasting, and changed the keyboard layout on all servers to Thai.
My security philosophy is: "When even admins with all the info can't get in, no one can."
It's not so much I would say I have trouble explaining it but rather I don't have a single way to explain it since the occupation doesn't have a name, at least in the English language, so I end up having a bajillion equally valid ways of crash coursing about it.
Nope, building prototypes, running experiments and develop stuff is rather easy to explain.
Explaining where i work is the harder part.
Oh yes, I usually end up saying "I work in insurance" because any more specific than that and people look at me with question marks in their faces
Same here! It gets complicated very quickly, so I usually just say "I work in insurance" and leave it there unless they ask more questions. If they do, it doesn't take long before their eyes start to glaze over and I change the topic to something more accessible.
Explaining that I'm a systems and infrastructure admin is actually easier for me than explaining my organization to people lol. Because it's a local government agency that provides services to school districts, and people don't really know we exist if they aren't a district staff member themselves (and even then sometimes they don't know!), and we're a bit niche in our specific services, I usually just end up saying "school ISP" despite that only being a small part of it. 😂
Guess my job: I something like Word for programmers
i build websites
AFTN/AMHS expert at an ANSP so definitely yes.
When people understand that it is about air traffic control and say "Oh so you work in the airport tower" you just answer yes.
Yes, sometimes.
I basically move and transform data.
No. Just keep it simple. Nobody wants to see you struggling to explain anything.
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
No. I've long given up to even bother trying.
