You must log in or # to comment.
People saying users are the bane of IT professionals are just antisocial whiners. The real bane of an IT professional is fucking printers. Fuck printers.
The users are why printers are.
Do toxicologists hate mushrooms?
Retail workers hate you.
Typewriter repair men used to hate word processors.
Most, if not all, professions in the domain of knowledge creation hate AI.
Photo editors hate:
I need to sit down and actually watch Red Dwarf sometime. Like I did once watch the first few episodes when I was a teenager but I was way too young to fully appreciate it
Human being here. I hate people.
/s
IT people hate computers.
This absolutely applies to me. I’m so sick of computers and software and security and subscriptions and vendors. I just want my own animal sanctuary with chickens and otters and baby goats god dammit!
IT people hate computers.
IT people hate users. IT people hate other IT people. We’re just a surly lot.
I’ve had the privilege of working with users with actual computer training. Old ladies who started working on terminals in the 70s and 80s. They were awesome, because they actually understood what they were doing. They could give me an accurate description of what they were doing when shit went wrong. They had real concerns and realistic requests for improvement. And they never blamed the computer when they encountered something they didn’t understand. They’re all dead or retired now.
Todays computer illiterate workforce is doomed to be incompetent because they don’t understand how their main tool works. Nobody bothered to train them.
Thing is, back in those days computers were deterministic.
A certain action caused a certain reaction, and always the same reaction (given the same context).
Anyone could learn that, as long as they bothered to read the screen (a surprisingly rare talent, to be fair).
Now, at least on windows, it’s anyone’s guess what random mayhem a certain action might cause, or where the interface to perform that action has gone after the last update, supposing it still exists and the system survived the update.
No one can learn that. And anyone foolish enough to try will certainly be driven insane.
Todays computer illiterate workforce is doomed to be incompetent because they don’t understand how their main tool works. Nobody bothered to train them.
There also so many things restricting the usage of the tool. Every week my scanner tells me it has a new software update and I cannot install a simple update without admin access, so I have to call help desk and have them remote into my computer so they can click the “ok” botton.
Everything is so walled off there’s no reason to learn how any of it works because you have no access. When the security bios update (forget what it was called) fucked everyone’s computers last year I found a fix online and could have easily went to several locations and got them up and running, but no one on site has the access to boot into safe mode and instead we all just sat on hold with help desk for 2 days waiting for IT to do the thing I already knew how to do.
It seems to run on some form of electricity.
The complicated thing here is there are so many layers of abstraction to make things easier to use and understand that if you didn’t age with the tech, it’s really hard to fully understand. That’s everything. I see Angular and React developers who don’t understand CSS.
My last position, we had classes that set sizes for everything in multiples of 4 pixels. So size-1 is 4 pixels, size-2 is 8 pixels, etc. And everything was sized with those classes. Which means if you ever wanted to resize anything, you have to go to every element and change the class instead of you know, having input controls have distinct classes.
People are layering on abstraction without understanding why and throwing away all the benefits, time to invent another abstraction layer! I had my tech lead argue with me that this was a better system because “standards”. I’m going to assume the standard was poorly understood because I can’t imagine a multi-billion dollar company hires idiots to set standards.
I got started learning transistors and Boolean algebra and programming an 8-bit cpu in college. Had computers for a few years before that. It’s surprising how many conditionals I see that can be simplified by Boolean algebra.
I don’t actually hate computers, and I try to give IT workers some grace because I’m not always proud of the work I do when I have to finish 3 months of work in two weeks. But I’ve worked with a lot of folks who aren’t curious or looking to learn and improve, and I have to wonder why they ever got into IT in the first place.
For me the worst part of IT is the god damned management. Any possible productivity gains from agile are undercut at every turn by management who has to have a concrete promise of a delivery date before they even define the ask.
Anyway, sorry for the rant. Started my long weekend early and starting a new job next week, so I have a lot of pent up rants from my last company.
We’re all standing on the shoulders of giants, but there are so many layers of giants that it’s hard to see the ground.
Why does it feel like im getting stepped on by giants?
true, but we also hate computers
We hate ones setup by other people or used by other users. Our own network is a glorious shrine to the one true faith.
My laptop windows 11? No problem. Anyone elses windows? Fucking burn it.
Can’t argue with that… until something goes wrong and I hate it (really just mad at myself)
“Dammit, what idiot set this up this way?” <checks logs> <you were the last login>
You just made an enemy for life!
You IT people sure are a contentious bunch.
FUCK PRINTERS
*ZIP*
Correction: IT people hate printers.
As a non-IT person, fuck HP in particular.
Correction: printers hate people.
Proctologists hate deodarant cans
Engineers hate managers.
Remember next time you get a shitty product, don’t blame the engineer who designed it. Blame the manager who forced him to do it that way.
I blame designers for everything. Keeps the fads and fashion for the well-to-do. The average person needs function first. Why would anything I want to buy for regular use be available seasonally or only come in over the top fancy plastic shapes with weird colors and breaks with less than 100 hours of use. I have a kitchen and office because I use them, not because it accents my overpriced home. I have worked in merchandising from many angles and it sickens me. Even what should be simple packaging on almost all retail products is overdesigned and printed full of lies. And the worst part is the cost of the product is directly related to design. Look at how cheap some knock-offs can be produced. I would never presume the engineer to be the source of the overpriced malfunctions of consumerism.
And don’t get me started about UX designers! Motherfuckers break whatever is working so it looks “clean”.
I think the average consumer simply believes its not legal to lie on packaging like that. They might not have even asked the question of whether its true or not.
Technicians hate engineers. An engineer will drag themselves across a field of naked virgins, ignoring them all, in order to fuck one mechanic.
As an engineer I can understand that.
It can be a little like a dentist and a dental assistant. The assistant does all the work but the dentist gets the Porsche.
As a former tech manager, I’d argue you’re a pretty shit manager if you tell your people how to solve a problem. Guide, inform, clarify, help remove obstacles etc. etc., but the solution is for the engineers to find.
Look, I don’t wish to be insulting but with a comment like that, I find it hard to believe you worked in any business. While engineers maintain some level of control over product design, like making the product actually function (although I’ve even seen that thwarted by management) they do not usually have the last say in things like ergonomics, interoperability, improvements that cost extra, appearance, business development and many other design parameters.
By management I should point out that I am including anyone who is above the design engineer in the process.
I’ve seen business development guys promise customers impossible functionality because “that’s what I thought they would want.”
I’ve seen schedules created by systems engineers that could not be met if we lived in a Star Trek universe.
I’ve been in meetings where production logic was similar to; if one woman can give birth to a child in 9 months, nine women can give birth to a child in one month.
I’ve seen budgets slashed to the bone or critical people removed from projects for a host of reasons, good or bad.
In an actual example I was in a meeting where the manager of business development didn’t know what the term PC Card slot meant. When he was presented with the product design in a meeting, he asked where the PC Card slot was. So the engineer pointed out that it was internal to the unit, on the motherboard where they were always placed. He did not like this because there was no actual slot on the outside. When it was pointed out that that wasn’t really possible without completely redesigning both the motherboard and the enclosure he insisted we put a slot on the outside. When told that the PC Card slot couldn’t be reached from ANY slot on the outside of the enclosure he made us redesign the end plate to incorporate a PC Card shaped slot that served no purpose except to stroke his ego, and add a costly change to a product with existing tooling and necessitate a PC Card slot sized plug to seal the unit against moisture be designed. We, from that day forward, referred to that end cap as the vanity plate.
Yeah a good manager would do all of those things you said assuming his manager doesn’t stop him, but that’s the point, managers suck. That’s why we hate then.
I don’t disagree with anything you’re saying.
What I wrote was based on my personal experience, managing engineers on product teams and how I approached the role as manager.
We owned the products we developed and maintained and as a team we enjoyed great autonomy, and so we were spared customers/clients asking for the ridiculous, and I can probably count on one hand (ok, maybe two hands) the times we just had to do something because corporate said so.
We always pushed for engineers’ involvement in product and feature development, planning/roadmaps, and they did indeed have great influence over the what and the how. Push back from engineers on products’ suggestions/ideas/plans were frequent, and attention was paid.
This was for a company in Norway, where perhaps top down management isn’t as prevalent as in many other places, and employees are typically encouraged to speak up and get involved. Again, in my experience.
I found that being there to support and assist my engineers, not micro managing them, gave great results in terms of team culture and work satisfaction. I made it clear that I would always have their backs as long as they didn’t intentionally fuck something up.
I fully realize this isn’t the case everywhere, nor even typical.
All said, I really enjoyed being a manager. On some level it triggered a father’s instincts in me, and I took great pride in looking after people and seeing what they were capable of building as a team.
I worked for four companies in my professional career, three defense contractors and one commercial company, all in the US. But I interacted with countless others both US and international and I would have to say, your experience is definitely the exception. You should definitely be happy you had such a great experience. I find it’s difficult NOT to have pressures to cut corners or just under-design. Cost, physics or customer expectations frequently turn that pressure up.
Programmers hate ai
Psychologists hate facebook…and also ai
Marriage Counselors hate reddit…and also ai
Data scientists hate time zones.
Every dev hates time zones but I wouldn’t say it’s the number 1 enemy
I would guess that in Data Science some things would require you to use local timezone because they are dependent on the actual time of day, and some would require synchronization so use of UTC. Also, some timezones are way off the sunlight time and would skew the data that has dependency on daylight and not on hours
We should invent standard computing time (SCT) or something and use that.
UTC
But dealing with timezone conversions and daylight savings is a pain. Like if you make a recurring task every day BASED on the user’s timezone, it’s annoying because of daylight savings
And name it Zulu Time because it sounds cool.
Chefs hate everything and everyone, but especially instagram.
My hell is a land of dishes that were sent back to be reheated.
As a psych nurse I hate food and housing instability and the death of thirdspaces. Oh and also the prison industrial complex.
And anyone in a field related to studying living creatures in nature hate pesticides/herbicides. Because pesticides harm everything that eats the thing that eats the thing that eats the thing that eats the pesticide.
Same thing with lead shot accumulating in large birds.
Wait, so the lead shots imbed in the animals that eat the lead shot large birds? And again for the animals that eat the animals that eat the lead shot large birds?
If an animal gets shot with lead, survives and runs away, there is now a wounded animal or an animal carcass containing lead somewhere in the wild.
If it is wounded or freshly dead a carnivore will eat it and accumulate lead. That may be large carnivore or a smaller carnivore that later gets eaten by a bigger one. Birds tend to have stronger stomach acid that most mammals, allowing them to dissolve the lead better.
Vultures having it the worst as they will eat any carcass and have the strongest acid.
