
@GossiTheDog This bot has been asked to generate an alt text for your image by @jstatepost. If you consent, you will grant altbot a one-time permission to process this specific post. All processing is done privately with no third-parties. Any and all content is deleted after processing.
The full privacy policy: https://github.com/micr0-dev/Altbot/blob/main/PRIVACY.md
Do you consent? Reply with 'Y' or 'Yes' to proceed.
Maybe I'm too cynical, but it's likely not management or shareholders suffering in these cases, but workers.
Management will simply force workers to somehow get things to function again, no matter the human cost.
Even when it is regulated this can be a problem. It already is.
Embarassment with the knowledge that mere "employees" have become indispensible often turns to resentment.
All of this would be dealt with by an analyst, but these self-dreaming 'entrepenreurs' never seek self-reflection
@GossiTheDog As someone who has been an "expert" at some undocumented tasks at work: it's not only the company that loses knowledge. I was once asked about a system I designed and implemented entirely on my own and couldn't answer a single question over the phone two years later.
Implicit knowledge has a strange affinity to fade away, unnoticed.
@a_lex_ander @GossiTheDog I had a moment like that at work recently. I've been there forever at this point.
I was trying to fix an issue that was caused by a bug in an ancient Perl script. As I was looking through it I kept asking myself “Who wrote this crap?”
Then I saw my own name in the header with a year starting in "19”.
@GossiTheDog But but but ... The agents of our new $500M investment in AgenticAI should handle being the glue ... Right?
Right?
Jep.
Every time a person dies, a library burns.
When someone leaves an organization, they take all the knowledge they have accumulated with them.
Cultural knowledge. Everyone jumps on the software side of business implementation when it comes to this loss but it's just as much about losing history as it is about the tech of things.
Knowing that xyz was tried years ago and that the results cost more time and money. Knowing that it's the investment in a certain nonprofit and the volunteer hours that's truly keeping the client. Knowing that leasing a piece of office space keeps your most valuable workers. Etc.
Everything a company values should be documented in a way that new hires can easily learn.
When a corporation talks about "values" though, they often don't include "preservation and sharing of comprehensive knowledge" as one of them.
And then they lay people off, bring in contractors, or outsource knowledge based operations, and wonder why nobody knows what's going on.
AI is going to be like that. People will only operate at the highest levels. You know, the levels where they push a button and expect everything to be automatically how they assume it should be.
This is what destroyed 3M. And likely Boeing after McNerny got there.
@GossiTheDog
If you are this person, there might be a temptation to make sure you're documenting all of the different threads you're holding together. If you're in an organization you deeply care about, that's probably something worth following through on.
However, if you're not in that extremely rare circumstance and it is just a job to you, there is hardly any better job security than being the only one who knows how to keep the gears turning. Even if they fuck up and let go, there's plenty of money to be made as a consultant at several times the hourly rate they were paying you when they find out.
@jargoggles @GossiTheDog And I'm pretty sure I was made redundant at one job because someone who played the game got close to the new director and fed them lies about what I was doing or not doing.
I wasn't a loudmouth or showoff, I just quietly did my work, did it well, documented the hell out of it, and moved on to the next project.
My direct boss knew what I did but she was also made redundant.
@jargoggles @GossiTheDog when I manage a team, one thing that's hugely important to me is to prevent this exact situation. I aim for deliberate redundancy. Every task should be able to be performed well by two people. And I'm transparent about why: Business continuity is important. I aim to protect my people, and in return I do not tolerate hoarding. It's toxic, not just to the employer, but to those left behind when the hoarder leaves. I insist on a culture of mutual respect. If that's not the way you want to play, I don't care how good you otherwise are, I don't want you on my team.
That respect flows both ways.
@mweiss @GossiTheDog
Unless you can *guarantee* that your direct reports will never get laid off, then the respect does not flow both ways. That is to say, there is someone above you who does not see your employees as people - they see budgets, KPIs, quarterly reports, etc.
If you are told, "We are eliminating head count by X, give me a list by the end of the week," your personal respect means a lot less to someone than whether or not your team can adequately function without them.
You are looking at a dramatically unequal power dynamic where someone is using probably the only effective tool they have - the irreplaceability of their labor - to protect their livelihood against an uncaring machine that has no qualms about financially ruining them just to move the stock price a point or two and thinking, "How can I make this about me."
I've managed teams, too. Part of the way I show them respect is by respecting that the most important part of the job to them is the fact that it pays the bills. If I can't factor in the fact that their primary goal is to make sure they can keep paying their bills, then I don't respect them as a person, I only respect the use I can get out of them.
Go back to LinkedIn.
@jargoggles @GossiTheDog I cannot make that guarantee. And I'm always very upfront about that, too. Of course I know they need to pay the bills, and that's important. The point of this entire thread is that companies ignore the hoarding and lay these people off anyway. So obviously the hoarding isn't protecting them, is it?
The respect comes from not pretending that the relationship between employer and employee is something more than it is. And that, too, goes both ways.
There's plenty of value that people can and do bring to their roles without resorting to hoarding.
#altText
A social media post from a user "Harmony?"
Text:
I've spent over 30 years managing large government operations. One lesson I carry with me comes from the retirement years ago of an employee most would have considered "obscure." He was a quiet man arriving each morning with his sandwich, working steadily, and leaving without much fanfare. To many, he seemed part of the furniture. It was only when he left that we truly realized his value. Over the years, he had accumulated deep, almost invisible knowledge. He had taken on countless menial but essential tasks simply because he had the experience to do them well. He was, in many ways, the oil in the machine. His departure forced us to scramble. We suddenly saw how many small, critical pieces he had been holding together, pieces no job description had captured, and no system had tracked. Since then, I've often thought of him when I see organizations subjected to blind cuts. The true cost of such decisions is rarely visible on a balance sheet: it's in the loss of quiet expertise, institutional memory, and the small acts of continuity that keep complex systems running.
My first team lead was one of those people. Never claimed to be a good developer, but knew everyone and their dog in the company, knew the businesses of our clients and our clients' clients, and was good with people in a very positive way.
If shit hit the fan, he knew who to call, how to deescalate the situation and how to communicate with the affected parties.
Would love to still work with him, but corporate forced him to low ball my salary a bit too much.
@GossiTheDog these people are vital — but — why did he not document all these little processes he took on? that was part of his job, too.
I can't know, of course, but often the answer is, the place he worked for didn't allow for him to do that effectively.
Exactly this indeed…
@GossiTheDog I have a similar story: I was working in Print for a while and one guy never had his numbers met. Why? He cleaned the trays.
See those trays had socket-slots and if you damaged them with the chisel you use to clean them they get wiggle room. So that one guy cleaned all the trays for everybody because he was that good.
They fired him and i think within a week the tray for the 3010 sockets looked like an Axe Murderer got to them. Missprints went through the roof.
@GossiTheDog It's one of the reason that offshoring / outsourcing jobs to dramatically underskilled + underpaid resources from poorer countries has caused so much havoc in IT circles over the years.
Bosses just thought the glue people could perform total KT (knowledge transfer) by writing everything down in multiple binders.
They never realized it's the WHY that matters about an operation / process / task at least 50% more than the WHAT.
(Hence my handle.) 😎
@GossiTheDog Yup, nearly a decade ago, I was working a new contract with a large bank. Two weeks in, they did a layoff, and two people from the department I was working in got canned.
One was the UNIX system admin with all the access I needed. The other was an analyst that knew all of the departments internal customers -- upstream providers of data, and downstream consumers of the data we were tasked with archiving.
Those two losses set back the project by a minimum of 6 months -- because every time we needed help, I didn't have someone to help me get access to the systems (by filling out requests and/or actually creating my account), and we never knew where certain data was coming from, and who it was supposed to go to (because the ONE person who knew was gone).
@GossiTheDog It is called the linchpin effect. 💡 ✅ #linchpineffect
https://debliu.substack.com/p/the-importance-of-linchpins-and-why
@GossiTheDog Many companies have already done this and many of them are now regretting it and scrambling to "fix" the slop that's been pushed to production.
within the past couple months or so I've been getting mails and messages from contacts on behalf of other clients about coming in to refactor or just straight up fix code, apps, etc that were pushed to production by AI Slop and "vibe coders". The tech debt is insane. It's gotten so bad I've been having to refer them to other devs who are looking for work.
I remember doing this a few years ago when companies were just offshoring to India but it was no where near as bad as it is now.
@GossiTheDog Sometimes I wonder about this. It's been true in my experience.
On the other hand, people were predicting that Twitter would completely stop working after Elon bought it and fired tons of staff. I remember hearing claims that there were no staff left who knew how to maintain (or were even aware of) critical systems responsible for serving tweets. That was almost three years ago, and while I only click a link to X every month or so, it still seems to work.
IT has many a tale of Project Leads who grease the wheel of progress yet get fired after every "on time, on budget" success.
On paper, they aren't seen as "productive" (fewer code commits) but they keep teams on task without creating anger, smooth over interpersonal friction, and inject realistic time management.
No death marches. No kids in rehab. No divorces. No mental or health crises. Undramatic function.
Such people are seen as disposable even while creating big revenue.
@GossiTheDog Same with Business Process Re-engineering (BPR) in the '90s. Workers laid off to pay for Re-engineering contracts. Later, managers notice more gaps in productivity, due to loss of Tacit knowledge that was held by lost staff. The contracts rarely paid off, and management imagines all kinds of excuses.
Until their failing company is acquired, absorbed, and liquidated. Too bad they didn't invest in the alternative Continuous Quality Improvement (CQI) and empower their own Teams.
The next hype will be GlueAI. It will figure out what all of your AI systems are doing, generate code to interface between the systems, and solve all problems.
Then GlueAI 2.0 will be released to fix the bugs.
It will be turtles all of the way down.