Hacker News Reader

Comment by boffinAudio | Hacker News Reader

Things went wrong when we started calling Computerization, "Information Technology".

This was a totally misguided re-branding of the field. It attracted bureaucratic personalities and classist managerial types, and utterly destroyed the field.

Like you, I couch my job description: I'm a "Systems Software Developer, I develop software systems" .. because its true, thats what I do, even if its a majority of the time working on embedded projects.

And if someone then responds with "ooh, so you're in IT", I immediately go to another corner of the party and avoid them like the intolerable bores they are ..

View on HN

> And if someone then responds with "ooh, so you're in IT", I immediately go to another corner of the party and avoid them like the intolerable bores they are ..

No need to be arrogant towards people outside the field. My grandma doesn't know the difference between the random IT guy that updates your Windows printer driver and a Linux kernel dev, but I'd still not call her an "intolerable bore".

Guess Problem is that a lot of managers also don't know, and have same understanding as your Grandma. I've seen plenty of companies take a very highly paid engineer and have them install printer drivers on peoples PC's.

I was getting paid £200k/yr as a Software Engineer for a company with an unresponsive offshore IT help desk. I would often spend a few hours (!!) a day helping various stakeholders with their desktops/printers/email. This was an insanely ineffective but absolutely necessary use of my time (I was managing a small development team with stakeholder satisfaction kpis), sadly my IT efforts were clearly more appreciated than development.

Hard to convince management that a dedicated onsite IT would be required - especially when they think it is your job already.

I suppose there is a difference between companies that are tech to the core (where everybody in the management chain up to CEO is actually a sw eng) or a company where software engineering / programming is just a dept. somewhere on the side.

Gotta appreciate if you're working in the former. Drawback is you can't BS your way through issues. Everybody above me in the chain (which is like 4 people) could write a quicksort blindly. If anybody tries any BS they don't have their job much longer.

> Guess Problem is that a lot of managers also don't know, and have same understanding as your Grandma.

Well, nobody forces you to work for a company with managers like that. I personally wouldn't.

That is a worthless recommendation.

That's kind of like saying, even slaves have a choice. Death being the option available to all.

There are enough companies out there without such managers.

Drawing a comparison to slavery is quite shocking, tbh.

The term 'wage slave' is commonly used. It is not always a humorous take on the situation. If you live or have skills where you have a lot of options. Then that is good for you, not the default for everyone.

I go a step beyond. When I’m interacting with “non-IT” folks, I say just I’m “in IT”.

It isn’t a problem for my ego to do that, and it’s something that’s both relatable and typically stops the conversation from revealing anymore about my work (not that there’s really anything to hide, I just enjoy my privacy and no, I don’t want to meet your “computer genius” nephew or fix your phone).

If I’m in a clearly technical group, I’ll go into more detail. I don’t identify myself with the DevOps term though, or sysadmin, or developer. I don’t clearly fit into any of the -currently assumed- definitions of those.

I'm very similar.

In social situations, I usually just say "I'm into computers". Most people who ask what I do don't really care, they're just engaging in ritualistic small talk anyway. If someone does care, they'll ask clarifying questions.

Same here.

I always default to "I work in IT". If that person is in the space I might go into specifics; but even then majority can't relate or understand the role i spend my days working in.

It also has the benefit of coming across as more blue collar and I catch less grief, as the disdaine for tech workers continues to grow.

I keep it simple and say that "I fix laptops" since I know that no one wants to hear about infrastructure gluing.

Yeah, that's all well and good until someone asks you to fix their printer .. because "you are an IT guy, you should know .."

"I make the systems IT uses"

That's the right approach.

Reply on news.ycombinator.com