Weird and Cringe things you've seen while working in IT - Since everyone is too lazy to make such a thread where IT bros can vent

  • 🔧 Actively working on site again.
Oh boy. In a position where the business leads are completely fucking up the business side and the technical leads are completely fucking up the technical side. It's the result of a program being treated like a project, along with SOPs being "academic".

Obv, I'm not sticking around to fix this shitshow when there's a 'smartest person in the room' mentality because we're doing something completely new and never been attempted before. (Ex. UEBA is a priority over basically everything else and even deserves a new, even more convoluted name)

Fortunately, I can quantify dozens of incomprehensible misteps, so I'm gonna enjoy burning everything to the ground and ruin a few careers on my way out. I'm so excited.
 
Last edited:
Please keep us updated @HackerX. :story:
I figure it's imminent and sparks via 2 options:
Option A- I snag another job and bounce. Shouldn't be a surprise. The very first thing I mentioned about operations is to assume anyone will quit the next day.

Option B- I get the axe while I'm working on Option A.

Option B popped on the radar after I suggested some common sense stuff, like using well-known frameworks. However, anything outside of analytics are clearly academic. (Current flavor word). They were expecting a discussion about dashboards for a platform that won't exist for the foreseeable future (if ever) and that's the moment I knew there's no fixing it.

Personally, I HOPE these mongoloids go with Option B and make the critical mistake of getting in the same with me. I'd love to repeatedly blast them with cool slurs, like retard, and list their ineptitudes.

Ultimately, I'm dealing with corporate politics-brained individuals, who mistakenly believe job titles mean anything when they are this incompetent. That strategy isn't optimal when I can shine a spotlight on all the shit they didn't do, done completely ass-backwards, or never on the radar.

For reference, this thing was a disaster before I joined. Big Brains blamed the client, but I managed to identify the sources when Big Brain #1 had an aneurysm after I told him you shouldn't half-ass technology selection for ticketing, LOL. (It was obvious they didn't account for certain concepts... Like change management.)

Big Brain #2 was identified when I noticed she was using certain words interchangeably and pretended to know what they mean. Not great when one of those words is operations and you're building an OPERATIONS center. My only explanation is she's the Peter Principle of sucking cock and found a ceiling that sucking cocks can't breach. (Academically, she's a retard.)
 
Last edited:
Hate double posting, but have an update. (More of a realization than an update, TBH)

Here's some context for those who have worked in a SOC. (Or any IT operations center for that matter, it's still looking at computer screens dealing with retards)

For months, I've been wrestling thoughts to figure out the dynamic for a specific design decision. One of those galaxy-brained decisions where complexity curbstomps any potential benefit, if it even existed.

Essentially, they provisioned 2 enclaves, but there wasn't a rational explanation for one of them, other than these wizards believing every alert is a legitimate incident/vulnerability/bad thing. For reference, indescribable LOL since it's the opposite issue. Much like every other absurdity I've unraveled, it clicked after the autistic pattern recognition overdrive engaged.

They legitimately believe the one-of-a-kind, never attempted, "bespoke" analytics justify an unnecessary enclave since there's no such things as a false positive. I guess the large coverage gap explains that braindead-level rationale! What's lulzy is, they are perpetually struggling to get approval for a necessary component on the 2nd enclave, LOL.

Misplaced priorities are an understatement when you believe everything works on magic and fairy dust, Jesus Christ.
 
Had to install a new cellular device after a previous tech “couldn’t figure out how to make it work”. Came onsite and found that the antennas that screws into the coax on the device was completely snapped, the wire in the antenna being pulled apart. Cue a bunch of meetings with the project managers and them trying to get in touch with the previous guy to figure out what the fuck happened. As soon as I saw it I took pictures to cover my ass and reported it to the support lady I was talking to, no fucking way I’m going down for someone else’s fuck up.
 
Had to install a new cellular device after a previous tech “couldn’t figure out how to make it work”. Came onsite and found that the antennas that screws into the coax on the device was completely snapped, the wire in the antenna being pulled apart. Cue a bunch of meetings with the project managers and them trying to get in touch with the previous guy to figure out what the fuck happened. As soon as I saw it I took pictures to cover my ass and reported it to the support lady I was talking to, no fucking way I’m going down for someone else’s fuck up.
At least he made it easy to identify the problem.

Also the update over yonder. Got fired! No real fireworks since I stopped caring when I discovered the Director is fucking clueless about operations. I also suspect he's boinking the project manager too, but that mess isn't my problem anymore.

The real lessons learned here is about requirements. If a team designs anything and doesn't notice they skipped about 3 layers of requirements, GTFO immediately. That's a self-licking ice cream cone that won't even lick itself.
 
Fixing old dude's phone and it was just tab after tab on google chrome of gambling websites. Every time he wanted to visit a website he would type it on the home google search and it would open another google chrome tab for that search. Had 100s of tabs open on this shitty phone that could barely run, his son thought it was slow because "it needed cleaning" so had a few shitty ad riddled phone cleaning apps that slowed the phone down even more.

I've realized over the years that nobody in management or recent graduates in tech have no clue about coding or technology in general. Tech jobs are very structured in hiring trying to get 30%+ women, 30%+ non-white etc. legit no matter the skill level. This leads to many cases of them drinking coffee for most of the day and browsing social media, they're the first to complain about layoffs because they sank a company.
 
Dealing with a client where, when the project commenced, they agreed to a "rolling billing schedule" in case of feature changes. We are about 1.5 years overdue and 100k+ over-budget and the client goes in circles asking for things to be removed, rewritten and then complains that the rewritten feature is missing parts of the old feature, where they explicitly stated those parts aren't needed anymore. This has happened nearly 15 times for major features, but they seem to be completely fine with it, stating "It's my indecisiveness, not your ability to implement what I want".

I have this terrible gut feeling like I'm taking them for a ride and feel like they're going to be very dissatisfied when this project never sees the light of day, but they're the first client my company signed with and they're responsible for about 80% of its revenue. Any thoughts/ideas on how we can actually progress the project to a reasonable state or abandon ship and part ways?

We are a small software consultancy.
 
Any thoughts/ideas?..
Just straight-up tell them "this is going nowhere, you have until X to decide on a set of features or we're shipping it as is", for a change. Having 1 sugar daddy isn't a viable business strategy in the software world - you must grow (find new clients and further develop the best parts of your product/service relevant to the market), or you will die.

Source: I made it the fuck up! personal experience.
 
Just straight-up tell them "this is going nowhere, you have until X to decide on a set of features or we're shipping it as is", for a change. Having 1 sugar daddy isn't a viable business strategy in the software world - you must grow (find new clients and further develop the best parts of your product/service relevant to the market), or you will die.

Source: I made it the fuck up! personal experience.
This is my gut instinct, the only problem is that the product they're building is very specific to their industry and it either works entirely or it doesn't. We can't ship it as is because it requires a completed E2E system.

I don't want to expose too much, but it's an application for automatically certifying constructions based on documents/questionnaires that we ask the user about their project site, utilising a configuration tool that plugs in the legislation from my country's construction code to determine compliance on a building.

I wholeheartedly agree with you about growing and finding new clients, which thankfully we are doing, but it's fucking brutal when you're a small company and your only customer cannot have their name mentioned as a use-case/example. I've seen the faces of prospective clients roll their eyes and sigh when I say, "we're working with an enormous firm, but I can't say their name, what we're doing or how their project is going because of NDAs".

You're right in saying that if you stagnate you die, we're currently in the part where about 90% of people either settle with what they've got or die out, so that sucks. Putting in 40 hours of programming/client-focused hours and then another 40-60 hours of cold emails, networking, conventions, marketing and getting on pointless Google Meet calls will really test your will!
1702557087725.png

I like this image because, despite it being for startups, I would say we're somewhere between the crash of ineptitude and wiggles of false hope in terms of our growth.
 
I come in for the interview. Both of my interviewers are some of the ugliest women I've ever seen. I'm told I'm supposed to interview with the IT director as well to get more info about the role. Turns out the CEO roped the IT director into going to a customer meeting that he had nothing to do with(red flag) 4 hours away, and I will not be meeting him today.

I find out almost every department is headed by family members of the CEO. "Training" begins. My trainer doesn't show up until 1PM, so I sit and observe help desk. Of the 10 people on help desk, only two of us are not black. I discover that one guy has been there for 6 months and still doesn't know how to consistently do password resets correctly.

The training here sucks and I'm basically told to just ask the other employees for help whenever I run into issues related to company products.

By day 4 I'm taking calls on my own because the training is completely worthless and I've got more knowledge and experience than most of help desk from being a nerd.

Customers don't actually open any tickets themselves through the ticketing system, they call, or email us. Frequently emails would just get deleted or sorted without getting turned into tickets by help desk, and no work would get done.

Primary customers are regular government employees, next biggest group are educators. I actually know some of the government employees from the work I used to do for the city government. I recognize the one, and I know the reason she won't check cables to troubleshoot is because she's such a fat black woman she can't get under the desk and move around effectively. She always screams and immediately demands a field tech or she will contact the CEO. Many customers threaten to contact the CEO because he knows them or their bosses personally, and this is something he actually encourages. The rest of help desk just obliges customers and sends the field tech for almost everything, even password resets, because at this point they know something I don't yet: nobody at the company does anything about help desk metrics (and also the end users can barely use email).

After three months, I hate 3/4ths of the department because they're glorified call center employees, and start agitating the relevant decision makers for more IT duties. I'm told they'll look into it. Somewhere around here I also realized there were a ton of active user accounts that haven't been used in years, and nobody wanted to so much as lock them. Passwords were stored in plaintext and all loaded into the web browser when accessing admin consoles, all you had to do was inspect element and there it all was.

Two of the field techs are literally retarded, only go to appointments after 11AM, and anything they get sent to, they fuck up and we need to send one of the other 2 field techs in the area. CEO has a boner for black men with no criminal record, so they do not get terminated for performance or for attendance. Instead, the customers complain and help desk would get yelled at lol.

The two retarded fieldies, when sent to appointments, would just start remote support sessions to have help desk do the work they needed to do in person, before leaving, because the field techs didn't know how to do the work and wouldn't admit it. We had lots of documentation for these issues, and they won't or can't read it.

When working with the educators, I would regularly ask them to power their computer on, and they would ask me how. How do I power it on? How do I make sure it's plugged into power? "Oh yeah, it's plugged into the wall, it won't turn on." I can tell the educator is retarded. I give up, send a field tech. Field tech's notes indicate it wasn't plugged into the wall.

One time I spoke to a principal and tried running through basic trouble shooting with him, and the man was clearly high on something, or severely brain damaged from the lead paint. All he could tell me was "the green thing is ripped." Could not tell me what the green thing was, what it was related to, or what he was trying to do.

One of the help desk employees got scammed over email into buying gift cards for the director of a non finance department during regular work hours. They did not think to even ask anybody else, they just went and did it.

Every day I would ask customers if they have restarted their computer. They would say yes, I would remote in, check up time and event viewer logs, see it's been days, weeks, even months, reboot it myself because they lied, and the problem would go away.

Lots of customers using 10+ year old computers on Windows 7, some even on XP, that could barely open a browser, least of all get any support. Of course, the company didn't ever have any kind of agreement pertaining to upgrading something like this, we were just expected to support it.

9 months in, and everybody on help desk except for 1 other guy has quit or has been fired, including two of the replacements. I am on my third manager. CEO tells me I will be promoted further into the IT department, but he doesn't know the details of my role, his son will take care of the details. They do not hire more help desk employees, I do not get a pay raise or a promotion, so I start bugging the IT director for work I can do. IT director hasn't heard anything about me getting a promotion. Instead, the CEO tries to saddle me with working the unfilled roles for two other departments, for way more idiot work, and the same pay. I refuse and have to fight myself from asking him if he's retarded.

I go out for a drink with some of the employees because I have a date nearby that bar later anyway and find out from one of the CEO's kids that in 2020, nobody was getting paid. The only people leftover from during that period are family members. As best as I can tell, the CEO's family has 6 luxury cars sitting out in the lot that I never see anybody drive except for the family(plus their own individual cars), and all the in-house hardware is in severe need of upgrades.

I eventually get worn down and start doing some other department's duties out of sheer boredom, because I'd been running out of jobs to apply to on my phone at work, had very little left I could automate for myself, and call volume was down because customers weren't using our products. I was given printed pictures of excel spreadsheets, header and all, and told to fill them out for documentation purposes. The employee giving me the print outs would absolutely not send me the actual spreadsheets, and would not accept the digital spreadsheets I would email them or print out, it HAD TO BE filled by hand.

Somewhere around 10 months I found out while scanning the network and going through old docs that there was a Windows 2003 server. Asked about it, only the IT director knew about it. I was told we keep it because the last time they tried to decomm it, it took the site offline. Somehow all the traffic is routed through it and nobody with the permissions to figure it out knew why or how.

Customers kept calling the help desk line asking me to help them with problems only other departments would be able to help them with. I told them to dial the respective options on the main line. They told me nobody picks up or those lines transfer to help desk. I checked myself, confirmed, and report the complaint to my boss, his boss, and also the IT director. Nothing is done. Couple weeks later I realize the reason nothing gets done is somebody is holding it up because they're literally sleeping under their desk most days, and not coming into work on other days. Nepotism.

One time a developer dropped a table in the production database for a server and caused a digital holocaust, generating 1500+ calls (including bounced) for help desk every day for almost a month.

I eventually get a "promotion" after I've got my hands into a lot of critical things because of other people quitting, and I call out all week, but I'm not told that my new boss in that role is quitting (he put in 6 weeks notice while I was out). Nobody is told he's quitting until the week before his last day, so nothing has been handed off, nobody is being trained on the stuff only he can do until now. Two of the CEOs family members have taken exception to me and are acting nasty and making things up because I keep complaining about the fuckups of someone who got fired(I think they wanted to fuck him) that I'm now dealing with, as well as a complaint I made to the CEO in private about his kids slacking off and costing us sales and billable tickets.

Anyway I eventually put in two weeks after I get my yearly "bonus." Worst mistake I made the entire time I worked there. Suddenly the entire family was giving me the cold shoulder or an attitude and I couldn't get any work done at all lol.

My experience working at this place made me a more racist, more sexist person, and made me wish for the death of trannies more regularly. It also made me realize just how retarded most educators are. The only thing I gained from this job was money, and only a little. Never work with or for brown people, if you can help it.
 
I've realized over the years that nobody in management or recent graduates in tech have no clue about coding or technology in general. Tech jobs are very structured in hiring trying to get 30%+ women, 30%+ non-white etc. legit no matter the skill level. This leads to many cases of them drinking coffee for most of the day and browsing social media, they're the first to complain about layoffs because they sank a company.
Doesn't help that HR/recruiters are these kinds of people, and will hire more of these kinds of people in the company. And they only know how to pick up/hire other of these bullshitters. They are prepared to fall hook, line and sinker for the bullshit of these people.
 
Dealing with a client where, when the project commenced, they agreed to a "rolling billing schedule" in case of feature changes. We are about 1.5 years overdue and 100k+ over-budget and the client goes in circles asking for things to be removed, rewritten and then complains that the rewritten feature is missing parts of the old feature, where they explicitly stated those parts aren't needed anymore. This has happened nearly 15 times for major features, but they seem to be completely fine with it, stating "It's my indecisiveness, not your ability to implement what I want".

I have this terrible gut feeling like I'm taking them for a ride and feel like they're going to be very dissatisfied when this project never sees the light of day, but they're the first client my company signed with and they're responsible for about 80% of its revenue. Any thoughts/ideas on how we can actually progress the project to a reasonable state or abandon ship and part ways?

We are a small software consultancy.
No idea about the contract language for this one, but here's what I've got:

Option A: Tell the client-niggers to provide written requirements. It sounds like y'all are doing Option A, TBH.

This usually results in a shitshow because business-niggers don't understand nuance behind certain words. Funnily enough, it's always the business-technical words. (requirements, PWS, SOW, Operations, etc.)

Option B: Determine the client-niggers values for whatever you're building, then identify your TOP AUTIST. Value mapping is an art which the TOP AUTIST turns into a science. (Personal experience.) It sounds like value mapping may help because building things from requirements usually results with no one being happy. (Personal experience)

To summarize my deeply esoteric approach.
1) Identify Values
2) Identify the industry best practices/ frameworks relevant to your product. (I hope this already happened, but most organizations are retarded.)
3) Map Values -> Framework Content -> Features.

Afterwards, y'all should be able to derive requirements from the client-niggers' values and help them clearly define what they want. Specifically:
- Operational Requirements
- Functional Requirements
- Technical Requirements (This is the one most organizations skip to and wonder why everyone hates it)

That may help, it may not. Who the hell knows. I'm just an employee for Niggers Consulting.

Option C: Tell the client-niggers they are niggers. (Preferred Option)
I would've noped the fuck out right then and there. That is like....one of the easiest things to do consistently in IT.
It never gets better, even as things scale into 100k+ salary territory. One recent example involves a junior employee wanting info on a document I mentioned they should include in a deliverable. I had repeatedly linked them the doc and told them to look at it for months since it's wildly relevant to the work we're doing.

People with no intellectual curiosity is one thing, but people that require their hands being held for simple things are the bane of my existence.

On a another note/update from my former project. They are attempting to deliver a Concept of Operations after firing the only person with a.... Concept of Operations. (LOL, they are legitimately copy/pasting a RACI from a different organization). I'm not rolled off the project full yet, but did unplug from all of the communications. More or less, just building a transition folder for the next person they set up for failure.

An HR person sent a random invite to me the other day with a obscure title. I assumed it was the grim reaper for obvious reasons. (i.e., layoff call) Turns out it wasn't and he seemed really interested with my description of a dysfunctional, failing organization, and leadership that is unable to comprehend words on the contract. Who knows. Not my problem.
 
Last edited:
Tech interviews are such BS.

Nobody values your skills and experience, instead they expect you to memorize and recite a middle school programming book.
The whole point of them is to create a legal way to discriminate against older Americans and heavily tilt the hiring pipeline towards H-1Bs, who are obviously extremely motivated to grind through 1000+ hours of leetcode questions to leave the literal shithole that is India.

The good news is that you too can grind through these problems! While it fucking sucks, you will be able to eventually get some sort of job if you can do most of the easy problems. The bad news is that if you don't have any previous experience or a relevant college degree, getting the interview will be the hard part.

Oh yeah, and the other bad news is that the interviewer will give you harder or easiest questions depending on if you're the same caste as him!
 
Tech interviews are such BS.

Nobody values your skills and experience, instead they expect you to memorize and recite a middle school programming book.
I've said this before, but I'm 100% convinced the people in tech these days are completely out of touch with how the real world works, because the majority of shit they expect you to learn just to get an A+ Cert you won't EVER experience or need to know in an Entry Level (Level 1) IT position, and even if you did encounter it...
  1. There will always be someone else in the department that's better equipped to handle it that's usually on a higher level than you
  2. Someone will teach you how to tackle the issue right there and then
The whole point of them is to create a legal way to discriminate against older Americans and heavily tilt the hiring pipeline towards H-1Bs, who are obviously extremely motivated to grind through 1000+ hours of leetcode questions to leave the literal shithole that is India.
^Also this. It's a complete fucking scam these days.
 
Additional contribution:

At some point I determined that passwords stored on the server for all user accounts were duplicated and locally stored on client devices that had the company software, and hashed with SHA-256(I think, IDR, but it was common), and all easily viewed in the local SQL database for the software. All the passwords were just sitting there, which seems like kind of a big flaw to me, but I'm just a know-nothing nerd under 50. Response to this was basically "Well, does anybody other than you know how to do that? No? Non-issue." Maybe I am full of shit, but I'm pretty sure it's a bad idea. Just off the top of my head, from my education, I thought you were supposed to hash a password the user entered, send it to the server, and compare it to the hash stored on the server for that user.
Thank god I wasn't in an actual cybersecurity role, I'd probably have lost my mind.
 
Nothing current, but I've found the blessedly redundant skeletons of backwards group policies.

From what I can tell, ten or more years ago some publically-accessible PCs at my workplace had a problem with the public installing specific programs on them; ideally, the public should have been incapable of installing any programs on these PCs back then, not even programs that could be installed without escalation (oh, OneLaunch, fuck you).

Instead, it appears that the previous admins blocked program execution on a per-program basis. So the public PC user accounts couldn't install Spotify and some other common software, but if they ever tried installing definitelysafeprogram.exe there'd have been no prevention if it didn't require escalation.

Really, having these computers be domain joined still rubs me the wrong way, but in the past it was the worst of both worlds since the power of GPOs were being leveraged in one of the most piecemeal ways imaginable.
 
Back