My experiences with IT across multiple organizations is that theyâre understaffed and not hiring particularly competent people.
The competent people they do have are generally egomaniacs because theyâre the only person or persons in a department full of idiots, and they deal with idiots all day, so they assume everyone is an idiot.
Additionally, IT is SUPER territorial. Like, noticeably so. They have 1-2 people that know what theyâre doing, but their whole staff acts like theyâre as smart as their smartest person, which they are, unassailably, not. I give a lot of respect to the competent and knowledgeable ones, because I realize theyâre also managing a bunch of idiots that donât know theyâre idiots.
Across three different organizations, Iâve watched five members of IT fired for their arrogance. If youâre interested in doing this, simply hire an attorney, bring the smart person into the room with the arrogant idiot, and make it clear that someone in that room is not going to work for the organization in two weeks, and then explain the situation.
If you feel attacked by this, youâre one of the idiot IT staff. Iâm good friends with our current CIO and security lead. I hate to break it to you, but they donât like you either. You are described as âcannon fodder for grandpa.â
Easy to fire, easy to hire. This cartoon adequately captures the level of questions that incompetent people working in IT can feel superior about. But theyâre not serious IT issues within a large organization.
Thatâs why you hire kids that graduated with âcomputer degrees.â So they can make cartoons and catch all the bullshit, while the real professionals do the real work.
Itâs good to have people like you around because we can always trust that your views perfectly reflect reality and are pretty much universal truths.
Iâm not saying theyâre universal truths. Iâm talking about my experiences with IT at various companies/orgs. And, yes, ideally people sharing their views, experiences, and opinions is kind of the whole point of this platform.
At least Iâm sharing my experiences instead of just snarking from the sidelines. Howâs that working out for you?
Agree. Anyone who expresses opinions or experiences so confidently/authoritatively may be more closely aligned with the problem than its solution.
Yeah a place I worked for had managers that thought that way. Then something broke and since the guy who knew how to fix it was fired a long time ago⌠well⌠I was already long gone by then. But their system was down for nearly a week.
Now if the managers established any kind of process then personality conflicts wouldnât be an issue, everything would be documented in advance (ie. planning) and the IT would just be following an agreed upon plan. Both management and the staff know everything thatâs happening and why itâs happening. And if thereâs staff turnover itâs no biggie because everything is documented and the management knows where the documentation is.
But that requires work⌠by management. So in many places it doesnât happen.
The reason why you have arrogant IT staff is only because they know that you donât know how anything works and they do. They know that if you fire them youâll be fucking over yourself because if something breaks thereâs a good chance you wonât know how to fix it and it may take their replacement a long time to figure it out because you never gave the IT staff an adequate amount of time to document anything.
Sure when you fire these guys things wonât break immediately. It might be a year, even several years before that critical thing (that you never required to be documented, no time for that) breaks and the system is down for an extended period of time.
The IT guys are arrogant because their boss is too stupid to know how to manage things properly to know how things are set up. Some managers are too stupid to even know why their IT guys are arrogant. Theyâre arrogant because they know that by firing them, the manager is fucking himself over. Theyâre just underestimating how stupid their manager is.
If you feel attacked by this, youâre one of the idiot IT managers.
Across three different organizations, Iâve watched five members of IT fired for their arrogance. If youâre interested in doing this, simply hire an attorney, bring the smart person into the room with the arrogant idiot, and make it clear that someone in that room is not going to work for the organization in two weeks, and then explain the situation.
I donât understand this. What happens when you do that?
Boomers shouldnât be allowed to touch computers. That generation needs to fucking retire already.
Agreed. I recognize it is the Steve Jobs, Bill Gates, and The Woz generation. But the technology is so far beyond what they created, even though we use what the Boomer generation created every day, and I get that.
Itâs the Jobs, Gates, and Woz generation, but until they step out of the way we wonât get a new generation of pioneers in technology. It used to be the dream was to create the next big thing, now the dream is to make something that gets you bought up by Google, Apple, or Microsoft.
Couldnât the wind thing be true? Moving air rubs on stuff, gets charged and provides a less resistant path for the em waves
Theoretically, but probably just as likely as goblins sneaking into your router and eating all the 1s in your binary
I doubt that would affect Wi-Fi, but what does affect it (at least 2.4 GHz frequencies) is microwaves. They operate at the same frequency and interfere with the routerâs output waves.
My wife refused to believe me until I had her run a speed test and watch the signal drop when I started up the microwave, then rise again when I turned it off.
Also IT guys:
I have no idea why things donât actually work and when presented with a core dump or any previous debugging the user did I panic like a little girl, so I restored to a previous system restore point, because fuck the changes you made since then and the fact that if you do them again the issue will come back, Iâm just supposed to close this ticket, not actually fix things.
Yeah, I donât call IT anymore.
The implied problem you arenât understanding is scope. Restoring your machines functionality and determining that if you do blank the universe breaks IS AN ACTUAL SOLUTION TO YOUR PROBLEM that is in scope and highly efficient. The company probably doesnât pay you to piddle fuck around nor does it pay the IT guy to make you piddle fucking around work out.
Digging in to the problem and figuring out an exact reproduction of the bug so that a bug can be filed with the appropriate owner of the whatever code and a fix instituted at some point would be far more interesting and fun, even more so if its in code you actually control and you can actually fix it but its likely not actually productive unless you can make a strong case for it.
The cost of fixing your stuff in 15 minutes and having you back in action is about $12.50. The cost of spending 3 days on it is $1200. Surely you understand why it works the way it works.
The company paid me to do exactly the actions I did before the system restore, which I had to redo after the system restore, and then I had to continue debugging and fixing the issue myself. Your cost analysis is fair in some cases, but it doesnât really apply here. It wasnât a âundo the changes so they can get back to workâ situation, it was a âfix the issue so they can continue workingâ situation.
Also, restoring the machine to a previous state was not a fix for my issue. I wasnât in a position where I did not have access, nor was I in one where I couldnât revert the changes myself (even without the system restore). This was a lazy/incompetent tech, who finished their ticket and went home for the day having done nothing but inconvenience me even more, and cause me to spend even more time on the issue.
I only wish this was the only interaction Iâve ever had with IT where they proved to be more trouble than itâs worth, but sadly thatâs not the case.
The implied problem you arenât understanding is scope. Restoring your machines functionality and determining that if you do blank the universe breaks IS AN ACTUAL SOLUTION TO YOUR PROBLEM that is in scope and highly efficient. The company probably doesnât pay you to piddle fuck around nor does it pay the IT guy to make your piddle fucking around work out.
Fucking THANK. YOU.
This is exactly what Iâm talking about, we donât get hired so that we can accommodate some bullshit that an individual user just thinks they need. We are hired to keep your machine working in the capacity that your job requires it to work. Nowhere in our job description does it say that we have to be your little errand boy making your fuck-ass decisions function in our environment.
and the fact that if you do them again the issue will come back
Damn, answered your own question. Have you tried not doing the thing that breaks the computer?
Yeah, let me not do my job anymore, so you donât have to do yours.
Goddamn IT, man. Every single time.
If itâs ACTUALLY part of your job Iâll care, if itâs some bullshit thing a wannabe IT user did to fuck their shit up that has nothing to do with their job (99% of the time itâs this) then fuck you.
Itâs a business machine, not your personal test lab. Goddamn users, man. Every single time.
Serious question.
Why is the venn diagram of furries and tech bros a circle?
IT finds a solution and applies it
Tech bro sells a solution and never references it again
