I think in part it's the industry's attitude towards software engineering, and undervalueing technical work. Most companies do this by adding more responsibilities than just building the software and maintaining it as if that isn't hard enough. It's everything from managing the project to being repsonsible for releasing and communicating the changes. People have limited time to specialize and become experts in the systems they build and slicing products vertically so that each engineer has a tiny slice of the entire business is producing fragile systems across the industry.
I don't agree. As a senior engineer I don't really want other people managing my projects or attempting to release and communicate my changes. I design a system (in collaboration with colleagues and stakeholders), I communicate how long it will take and why, and I'm responsible for putting it into production and making sure it works. All of this is just part of being a professional who takes responsibility for their work. Delegating any part of that to someone else would give away more agency in my work than I'd like.
I'm willing to concede that there may be other areas of software engineering where it makes more sense to have the narrow specialists you describe, but it hasn't been my experience. Also for junior staff it might make sense for their senior peers to project-manage them a little bit so that they're not too far outside their comfort zone.
I have, and I usually explain that you can’t get nine women together and have a baby in one month.
They usually do as they please, and assign extras or not, and ultimately learn in the long run.
This isn’t to say that extra staff on a project can’t be helpful. But more often than not, management miss-estimates how the extra staff will impact the project.
I don't get why management is seen as some higher level job. It's actually lower level in my opinion. It's just a matter taking some notes and then telling others of the status. The problem is it's time consuming, time that could be spent ensuring there are no bugs and everything works perfectly.
In my experience what instead happens is that companies are ok with bugs so long as you communicate why it happened and how you are going to fix it. So the tradeoff is clear, spend a lot of time managing and let bugs happen so long as they are being managed properly. This is what I think causes fragile software at scale. People with high level technical knowledge should be hands on, and any bugs should be unacceptable.
I’m a “working manager” in my company. I now have a contract through my company with one of our clients. On that contract I’m probably short 2.5 people (it’s just me right now). I’ve raised it on both sides.
The shits that I give wax and wane on a quarterly basis, but the average pattern is me being largely disengaged, disincentivized to well, and burnt out. I’ve basically told my company they can’t really count on me for anything.
Maybe they’re trying to get me to quit or waiting for the contract company to hire me direct.
Sorry, different type of “added responsibilities “
Managers are extremely important. If anything I'm advocating for more management. Instead companies have offloaded a lot of those responsibilities unto engineers. Management is a hard skill and could free up technical people to focus and produce high quality software. If it's really necessary that engineers also do some management, I think it can be a role people switch into per project instead of always being a kind of hybrid.
Hope you find some resolution on your side. It can be tough sometimes.
Agree. The problem is that managers tend to move their responsibility onto engineers. Should I need to understand why do you want to build X that does Y? No, I should get a spec where you describe the outcomes. Each to their domain - devs to technical, product to business. Instead I learn why the sprockets are of flubber color because it resonates with women aged 10-30
Long ago while I was the Pres of the local IEEE chapter, I was out to dinner with the section chief and her VP and the VP said engineers were the only professionals who handed over their hard work willingly for no guarantee of anything. His view was that the smart engineers learned how to exploit the company resources for their own research in patent seeking...other than that he was quite angry that engineers never unionized.
can you imagine if the IEEE had formed a union, way back in the 40's or so...???
To be fair I worked with engineers who used codebase as their own playground. You're interested in this methodology, language, pattern? Fuck anything else, fuck any standards that the team has, fuck other people that will have to cleqn after you and the outages you're causing - you just go hog wild, your friend approves PRs, nobody else understand what's going on because you decided to write something in brainfuck and then, after you leave I can see you give presentation about how brainfuck driven development is the next big thing and how your consultancy will solve every problem one might have
Monetarily valued for sure, but it would be interesting to know what split of politics and actually applying their craft got them the millions.
SV is also not the whole industry so looking outside of that, I see exactly what OP is saying. Technical staff are usually required to split their time across numerous project management tasks that are mostly to support the project management team's communication of goals to the client up the ladder. I am not purporting to have a solution to the problem mind you, it's more complex than just "let em code man!"
I bet in general it is not because of their technical expertise as much as their management skills. Engineers are increasingly a hybrid role and you can't just spend your day solving technical problems (even though in most companies I've seen everything is constantly breaking and full of bugs).
I think you're conflating very different groups. Folks with 100+ million dollars to their name are going to be owners rather than "tech employees" and I'd guesstimate 100 of them before filtering for "tech".
"As the twenty-first century began, human evolution was at a turning point. Natural selection, the process by which the strongest, the smartest, the fastest reproduced in greater numbers than the rest, a process which had once favored the noblest traits of man, now began to favor different traits. Most science fiction of the day predicted a future that was more civilized and more intelligent. But, as time went on, things seemed to be heading in the opposite direction. A dumbing down. How did this happen? Evolution does not necessarily reward intelligence. With no natural predators to thin the herd, it began to simply reward those who reproduced the most, and left the intelligent to become an endangered species."
I would argue the opposite. LLMs are the ultimate example of 'smart and gets things done'. This is why CEOs love them so much. They really are quite smart and boy do they ever get a lot done.
OP is noticing that those who are smart and care about long-term outcomes beyond their job incentives (aka, "give a shit") have been sidelined or eliminated. Because they are in the way of "getting things done".
Then identify a mechanism for holding your executives accountable for their decisions. 10% of them should be fired annually, regardless of performance.
Based on what I see in the workplaces nowadays, people who give a shit are treated like shit. Give a shit about your own wellbeing instead first and if there is still some left to give, sure throw it at the project.
> Hinton took aim at the risk-taking by the leaders of some of the major AI companies who continue to release ever more powerful AI models as they race for supremacy and market-share, saying he didn’t trust Sam Altman, the chief executive of the ChatGPT maker, OpenAI, “at all”. “I think [Mark] Zuckerberg and [Elon] Musk and Sam Altman, they understand the risks, and they don’t give a shit. They’d rather have the money. That’s my belief.”
It is because when rubber meets the road and money dries up some, they cut exactly 5000 people, no more no less. Clearly there is zero grasp on actual capabilities of a given employee. They are seen as numbers in aggregate. A large pool where each part is fungible with any of the rest. A Joseph Stalin worldview I suppose, where people are reduced to statistics one can toss out without emotion.
It is not an environment where you are motivated to do your best work. You'd have to have a screw loose actually to go above and beyond in these places. Working hard gets you nowhere here, just spins your wheels in the mud.
There are certainly places that do value your contributions, but they aren't ever going to be the sort of shops that have newspaper headlines announcing a perfectly even number of layoffs ahead of earnings.
I agree. I suffered burnout in 2001 from working as hard as I could for a law firm until I developed schizoaffective disorder, and then I got fired. Now I am on disability, trying to learn new programming languages to get back in the game.
Even worse, they are written up or made to quit for "argumentative" or "not a social fit" reasons which barely fit what actually happened. One would have to provide their own documentation to get anywhere.
You absolutely can. Whenever you send a PR that you want approved to the guy who approves everything, you're embodying the Sociopath mentality just a little bit. If you do it because you want to push the fix and help your biggest customer you're being slightly Clueless, whereas if you do it because you need to go home to your kids you're being a Loser. (Have I mentioned I think the nomenclature is stupid?)
The archetypes describe basically everyone to some degree. They're like a zodiac sign or an MBTI dichotomy or an OCEAN axis.
read the essays a little more closely. the whole thing hinges on 'theory of mind' and what people choose to do with it. his 'be slightly evil' motto aimed at splitting the difference between the sociopath and loser. just put more effort into understanding human behavior and you'll naturally find out your own approach.
Anything that compromises the bottom line or puts the next executive bonus at risk is considered a waste of time.
From their POV quality, privacy and security are not worth investing in. Unless the government forces their hand, and even then they'll find ways around it.
> I know someone who was essentially fired because he spent too much time solving customer issues instead of shipping new features.
Me too! Very smart guy, well mannered, easy to work with so support kept reaching out to him and the senior manager fired him because he was focusing more on solving issues than new stuff. Also, support is a different org, they are born to suffer.
The manager wasn't going to get his own growth by not delivering much new stuff and just improved maintenance. So obviously he didn't focus on how we can reduce these recurring issues so that we have more bandwidth to focus on new issues. Because who cares about pressure on these developers, they are an unavoidable nuisance, you see (AI is solving that very long standing grievance).
Laser sharp focus on survival + growth + current bonus cycle will do that.
I had the same happen in my local neighbourhood group recently: arguing is seen as dissent and treason rather than caring enough to spend energy to try and improve things. Better to be a free loader. Unfortunate vestige of the human condition.
Giving a shit can be a career-ender. Prizes are given to those with least shits given. It can weigh heavily on one’s conscious, and their wallet, to give a shit.
This matches my experience too. I would love to have a job I give a shit about, desperately even. But I switched to doing my own thing and consulting precisely because everyplace I worked the more I gave a shit the worse I got treated. Now at least the only one abusing me is... me.
What am reading from all the comments agreeing with the parent is that there is a lot of misalignment about what people gave a shit about, and what they should have gave a shit about (if they wanted to be treated well).
And no I’m not just talking about office politics. Often people who feel they’ve been treated badly are giving a shit about “business outcomes” that they believe the company should/would care about (often not the case), or they gave a shit about the specific tasks they were given. Can’t blame them for that.
But what successful people give a shit about is more along the lines of solving superiors problems etc, regardless of what “business value” is or what your written job description is
> But what successful people give a shit about is more along the lines of solving superiors problems
Happy to solve superiors problems but they don't give me their problems, they give me Jira tickets
Unfortunately there's only so much time in a day and if I'm going to get shit for not closing enough story points then where will I find time to kiss ass like this?
True, smart people who give a shit need to find a not smart person who doesn't give a shit and subborn themselves to that person and then try to get whatever benefits trickle down.
It's not that smart of a path to take, so ... it takes a certain type of smart person to fit into that position long term and not lose their mind or get sick of it. You have to kinda want to be subservient to some degree, or else focus on what other smart people who give a shit are around that you can manipulate into being your servants.
And if you care about something like "is this a good experience for the user," "does this respect the users privacy," etc. Then what you care about can be in conflict with "business value" and or what your boss wants.
> Capitalism has never been particularly kind to smart people who give a shit (or people in general... but I digress). Capitalism does, however begrudgingly, recognize that smart people who give a shit are required to build and maintain complex systems that serve capitalist goals.
The article is quite close to a deep insight on that point, but it misses the moment. There is a surplus of people who care, the limiting factor is the ability of the management class to value the outcomes.
If the capitalists understand that something creates value, then they will treat the people doing that thing well (better than the people not creating value, anyway). If they don't, then those people will be treated poorly. The key is understanding and not the on the ground outcomes. That is why metrics and processes always end up being such a big deal in corporate culture; because the people in charge are aware that the limiting factor is their ability to understand their own company and they're just not necessarily very competent at acting on that knowledge.
The OP also neglects to mention that ACH failing would actually be better for capitalists because another 5 systems could rear up and become subscription businesses that siphon your financial data to advertisers.
It’s a feature - not a bug - of the capitalist system mentioned.
Not sure this is a hot stove moment, but it will certainly be a reckoning and likely result in some significant regulation, common efforts through partnerships with private entities, and a more measured societal view of the good of companies - only to revert back again in a 60 year cycle. Such is history and life.
> The OP also neglects to mention that ACH failing would actually be better for capitalists because another 5 systems could rear up and become subscription businesses that siphon your financial data to advertisers.
On one hand, yes, nobody should set themselves on fire to keep someone else warm, especially in a business transaction. On the other hand, literally everything nice in life happens because someone gave a shit.
Yeah these days it feels like nobody gives a shit at all. I saw the shift happen like 10 years ago.
When I worked in blockchain, everyone there claimed that they "Were in it for the tech." But in practice, by 2018, NOBODY cared about the tech at all. All the projects were over-engineered and bloated. It didn't matter; those projects raised millions. The few well designed projects which were created with minimal code and dependencies never got any attention or traction. In my community, they were even suppressed with founders threatening to go after innovators legally and defaming people who they should have supported. Nobody cares about tech. Everyone is using it to create complexity to improve their job security.
Figured this out about 5 years into being a developer.
Finally got my first well paying corporate gig as a developer. First year was told the overachievers are the ones making the big bonuses. Went all in. Busted ass, took on additional work, learned new languages/frameworks. I had a dozen goals I completed. Other devs were telling me back off and slow down, I was making the whole department look bad because of how hard I was working.
End result? Mid review. Barely a bonus & a kick in the nuts.
Next year? I did the bare minimum. DGAF about anything. Full shutdown, Honey Badger mode.
End result? Mid review. Barely a bonus & a kick in the nuts.
I finally realized the one person who benefited when I gave a shit was my manager because I made him look like a rock star. Me? I got nothing. Walking out of that year end review pretty much sealed the deal for me. I finally realized I can just focus on my own well being, still get paid nicely, burn all my PTO and not GAF about anything.
Its a pretty refreshing place when you can not give a shit about anything and still be gainfully employed. I was quietly quitting a decade before it was even a thing.
Doing things requires 1) making a business case that doing it provides value that is 2) over and above the value of other things that need doing and 3) working the politics to get others onboard. Without those things, it doesn't matter how right you are, you're still wrong. The business does not need everyone running off in all directions because each of them is convinced they're "right"; that's a rabble, not a team.
A lot of the sour posts are people that just don't get it. They want to do what they personally "give a shit" about, other opinions and priorities be damned, and that's why they'll be kept on a short leash forever.
it seems once you're smart enough in a niche or field worth investing in (giving a sht about), you're either paid to keep the status quo just as it is, or you're branded a heretic who wants nothing more than to cost people their jobs
People say this but in reality it's all about time to market. It's all about doing things as fast as humanly possible. Well, as fast as agentically possible, I guess.
Giving a shit actively gets in the way of that. If you care too much about things, then you're going to waste time focusing on things that don't actually make any money instead of shipping.
I wish companies would hire a professional shit giver whose sole task is to care about things and nurture them, make things better overall. It doesn't seem like they're ever going to do that, though.
They are sidelined, because giving a shit is not reflected in OKRs and giving a shit often equals standing in a way of "good enough" as judged by a middle manager and thus committing mortal sin of not focusing on getting to market faster.
Also what is the metric for giving a shit? It's not very SMART for OKRs.
If you are a metric driven organization, giving a shit is driven out of the organization in favor of tracked variables. Which usually happens around the time the company headcount hits Dunbar's number.
You are paid to solve problems. But if you work in such a way as to solve problems before they become problems, then you don't look like a problem solver. So you become the problem.
I would revise the thesis to add: we need smart people who give a shit and are willing to go the distance. It can take 5 years to modernize ACH. You have to commit and stick with it.
> Capitalism does, however begrudgingly, recognize that smart people who give a shit are required to build and maintain complex systems that serve capitalist goals.
Ha! No, it doesn't. The moment that the capital owners can bisect responsibility enough that each cog can be replaced with an "equivalent" (read: younger/recently graduated, capable of typing code) cog, the smart and caring are discarded. This is because People With Opinions can derail the goals of the investors; because Smart People begin to understand just how pointless the ISOs are.
The founder with the engineering intelligence and the business intelligence to build their vision is the only on who stays stealthy and small, needn't take investors, needn't hire dozens of additional engineers.
This is borne out by the frothing-at-the-mouth mad enthusiasm that business owners and managers seem to have for implementing such a new and unproven technology as AI to replace all-the-people-things.
The actual end result doesn't seem to matter too much, it's the time and cost savings that seem to be the motivators, pure ultra-short-term-ist capital-on-pedestal thinking, with barely a pause to consider 'the product'.
I noticed something happening over the last two decades: as improved automation and efficiency allowed fewer technical people to "do more", the ratio of technical to non-technical staff has shifted to the latter.
It's to the point now that I regularly see large and complex systems being built by essentially one guy but with dozens of "managers" overseeing his solo work. I've been in meetings with "project coordinators", "project managers", "governance", "change control managers", etc... all on the same single-product team and only one person there actually "presses the buttons".
This has shifted power and decision making away from the "smart people who give a shit" over to the "politicians that like to play Game of Thrones In The Workplace".
Look around you and see if you can spot more of these "inverted pyramids" with the point at the bottom: one technical person at the bottom "managed" by a team, which in turn has an even larger layer of managers above them, etc.
I suspect that inverted pyramid won;t last... Most of those roles are coordination - knowing who is doing what and relaying it upward - and that's the part AI is taking. What's left for a dozen coordinators around one person?
Bit of a tangent to the article’s point, but do we know for sure that none of these events were cyberattacks? I don’t mean at the level of questioning official statements, I’m asking if there even have been official statements on all these events.
My (poor) understanding is that most have not received an actual explanation. It’s entirely possible some were cyberattacks.
1. I don’t agree this is necessarily due to AI. PE has hollowed out every industry. Take a great business, fire everyone, mine it, let it die.
2. The “smart” people at the top are generally selfish assholes. They abuse the system and others to self enrich. We don’t need more smart people, we need more caring people.
3. Nobody gives a shit anymore. The older generations fucked it up and are aging out and just saying haha sorry we messed it up but good luck while I chill in my 7th vacation home. The young are jaded because all the jobs are dogshit and underpaid. The only way to win is to get rich overnight on Kalshi or crypto or futures or whatever. Why would you work for most of these horrible companies? It’s not worth your life.
4. Look at POTUS. Grift on grift. Everything falls apart in a society that runs on grift. They couldn’t even re-line a pool…
We've had spectacular infrastructure outages for decades; I think that a cluster of incidents in one week doesn't establish that AI is directly responsible for declining reliability.
IMO, the issue is that AI is reducing the cost of building and modifying systems much faster than it's reducing the cost of understanding them. For example, an engineer can work on a problem or project for a week that could otherwise be done by AI in an hour or so. But, that week spent was not "wasted time"; it was understanding what it is they are building, discovering undocumented assumptions, knowing about different dependencies, developing intuitions about the system and how it works, etc.
This causes comprehension debt. Yes, the system does ultimately work, the tests also pass. But the level of comprehension goes down significantly.
That said, AI can also help reduce this debt by asking it what you need help understanding.
I indict management, not AI. Redundancy and robustness required money and effort, neither of which add to the bottom line or get quicker to market. Cynically, it costs more to prevent failure than endure or recover from one. So business take the obvious fork.
And as far as air traffic is concerned, they’ve been trying to strangle it since at least 1980. Canada has a privatized system, so it’s possible to create such things but that is a matter of political will not money.
When you change a system directly you learn the underlying nature of the system and your toolset for making changes. Guide a third party toward making the changes and you learn the nature of the interaction and your toolset for evaluating the outcome of changes.
Does the distinction matter? Depends on your perspective I suppose.
> We've had spectacular infrastructure outages for decades
Absolutely.
However, we've also never poured more in, to such centralised infrastructure.
I've actually never worked in any company that has had a communications outage for 36 hours in my life; and I've worked in places we had a dancer IRCd running on an old laptop under the faux floor in the server room with Solaris as the main communications tool... thing is: it was so simple, when it went down we just fixed it.
Technology companies have very successfully convinced us that we should outsource responsibility, because there are economies of scale. Then they ask for a free pass because "scalability is hard".
You don't get to say scalability is hard when you've been pushing and propagandising centralisation for over a decade, while having thousands of staff on million-dollar yearly TC packages.
Everyone here will say "nobody got fired for buying x- because everyone does" (Slack, IBM, Microsoft, AWS), and you can use it as an excuse... but you know what happens when we over-rely on something like that and it fails?
Economic crashes. That's exactly how the 2008 financial crisis happened, everything depending on something that had "absolved" responsibility. Such a thing has ruined the prospects of an entire generation of people, and I'm actually becoming really upset that we think we're being clever bastards because "oh hum, well, I can't be held responsible for total systematic collapse, everyone else was doing it!"
> We've had spectacular infrastructure outages for decades
And yet, in the entire history of electromechanical switching in the Bell System, no central office was ever out of action for more than 30 minutes for any reason other than a natural disaster. (With one late exception, a major fire in New York City in 1975.[1])
That was achieved by design. Electromechanical telephone switches were designed to have no single point of failure. That was achieved in practice. Failures occurred all the time, but the problem was confined to a small group of lines, if not a single line.
I'm not going to go into how that was done; read up on #5 crossbar if you're interested.
Even complex functions such as long-distance routing had backdowns to static routes stored in read-only devices, in case the telco equivalent of BGP failed.
That reliability record has not continued into the computer era.
305 comments
[ 2.8 ms ] story [ 27.9 ms ] threadI'm willing to concede that there may be other areas of software engineering where it makes more sense to have the narrow specialists you describe, but it hasn't been my experience. Also for junior staff it might make sense for their senior peers to project-manage them a little bit so that they're not too far outside their comfort zone.
They usually do as they please, and assign extras or not, and ultimately learn in the long run.
This isn’t to say that extra staff on a project can’t be helpful. But more often than not, management miss-estimates how the extra staff will impact the project.
In my experience what instead happens is that companies are ok with bugs so long as you communicate why it happened and how you are going to fix it. So the tradeoff is clear, spend a lot of time managing and let bugs happen so long as they are being managed properly. This is what I think causes fragile software at scale. People with high level technical knowledge should be hands on, and any bugs should be unacceptable.
The shits that I give wax and wane on a quarterly basis, but the average pattern is me being largely disengaged, disincentivized to well, and burnt out. I’ve basically told my company they can’t really count on me for anything.
Maybe they’re trying to get me to quit or waiting for the contract company to hire me direct.
Sorry, different type of “added responsibilities “
Hope you find some resolution on your side. It can be tough sometimes.
can you imagine if the IEEE had formed a union, way back in the 40's or so...???
The Seattle area is full of tech employees who are millionaires and some even up to 9 figures.
SV is also not the whole industry so looking outside of that, I see exactly what OP is saying. Technical staff are usually required to split their time across numerous project management tasks that are mostly to support the project management team's communication of goals to the client up the ladder. I am not purporting to have a solution to the problem mind you, it's more complex than just "let em code man!"
I think you're conflating very different groups. Folks with 100+ million dollars to their name are going to be owners rather than "tech employees" and I'd guesstimate 100 of them before filtering for "tech".
IYKYK
And we'll only qualify the wealthy brownnosers as such.
OP is noticing that those who are smart and care about long-term outcomes beyond their job incentives (aka, "give a shit") have been sidelined or eliminated. Because they are in the way of "getting things done".
https://www.theguardian.com/uk-news/2026/nov/03/ai-godfather...
It is not an environment where you are motivated to do your best work. You'd have to have a screw loose actually to go above and beyond in these places. Working hard gets you nowhere here, just spins your wheels in the mud.
There are certainly places that do value your contributions, but they aren't ever going to be the sort of shops that have newspaper headlines announcing a perfectly even number of layoffs ahead of earnings.
The archetypes describe basically everyone to some degree. They're like a zodiac sign or an MBTI dichotomy or an OCEAN axis.
Wasn't even argumentative, just quietly gave a shit.
From their POV quality, privacy and security are not worth investing in. Unless the government forces their hand, and even then they'll find ways around it.
Me too! Very smart guy, well mannered, easy to work with so support kept reaching out to him and the senior manager fired him because he was focusing more on solving issues than new stuff. Also, support is a different org, they are born to suffer.
The manager wasn't going to get his own growth by not delivering much new stuff and just improved maintenance. So obviously he didn't focus on how we can reduce these recurring issues so that we have more bandwidth to focus on new issues. Because who cares about pressure on these developers, they are an unavoidable nuisance, you see (AI is solving that very long standing grievance).
Laser sharp focus on survival + growth + current bonus cycle will do that.
What do we do about this mess?
And no I’m not just talking about office politics. Often people who feel they’ve been treated badly are giving a shit about “business outcomes” that they believe the company should/would care about (often not the case), or they gave a shit about the specific tasks they were given. Can’t blame them for that.
But what successful people give a shit about is more along the lines of solving superiors problems etc, regardless of what “business value” is or what your written job description is
Happy to solve superiors problems but they don't give me their problems, they give me Jira tickets
Unfortunately there's only so much time in a day and if I'm going to get shit for not closing enough story points then where will I find time to kiss ass like this?
It's not that smart of a path to take, so ... it takes a certain type of smart person to fit into that position long term and not lose their mind or get sick of it. You have to kinda want to be subservient to some degree, or else focus on what other smart people who give a shit are around that you can manipulate into being your servants.
The article is quite close to a deep insight on that point, but it misses the moment. There is a surplus of people who care, the limiting factor is the ability of the management class to value the outcomes.
If the capitalists understand that something creates value, then they will treat the people doing that thing well (better than the people not creating value, anyway). If they don't, then those people will be treated poorly. The key is understanding and not the on the ground outcomes. That is why metrics and processes always end up being such a big deal in corporate culture; because the people in charge are aware that the limiting factor is their ability to understand their own company and they're just not necessarily very competent at acting on that knowledge.
It’s a feature - not a bug - of the capitalist system mentioned.
Not sure this is a hot stove moment, but it will certainly be a reckoning and likely result in some significant regulation, common efforts through partnerships with private entities, and a more measured societal view of the good of companies - only to revert back again in a 60 year cycle. Such is history and life.
Isn't that already being pushed with Zelle?
When I worked in blockchain, everyone there claimed that they "Were in it for the tech." But in practice, by 2018, NOBODY cared about the tech at all. All the projects were over-engineered and bloated. It didn't matter; those projects raised millions. The few well designed projects which were created with minimal code and dependencies never got any attention or traction. In my community, they were even suppressed with founders threatening to go after innovators legally and defaming people who they should have supported. Nobody cares about tech. Everyone is using it to create complexity to improve their job security.
Finally got my first well paying corporate gig as a developer. First year was told the overachievers are the ones making the big bonuses. Went all in. Busted ass, took on additional work, learned new languages/frameworks. I had a dozen goals I completed. Other devs were telling me back off and slow down, I was making the whole department look bad because of how hard I was working.
End result? Mid review. Barely a bonus & a kick in the nuts.
Next year? I did the bare minimum. DGAF about anything. Full shutdown, Honey Badger mode.
End result? Mid review. Barely a bonus & a kick in the nuts.
I finally realized the one person who benefited when I gave a shit was my manager because I made him look like a rock star. Me? I got nothing. Walking out of that year end review pretty much sealed the deal for me. I finally realized I can just focus on my own well being, still get paid nicely, burn all my PTO and not GAF about anything.
Its a pretty refreshing place when you can not give a shit about anything and still be gainfully employed. I was quietly quitting a decade before it was even a thing.
A lot of the sour posts are people that just don't get it. They want to do what they personally "give a shit" about, other opinions and priorities be damned, and that's why they'll be kept on a short leash forever.
Guess who is in charge of the AI companies?
just like how you cant have independent journalism when they have no income
VisiCalc and the start of the spreadsheet era went pretty well for many people.
There aren't enough humans who are smarter than the machines.
That situation gets worse every week.
Giving a shit actively gets in the way of that. If you care too much about things, then you're going to waste time focusing on things that don't actually make any money instead of shipping.
I wish companies would hire a professional shit giver whose sole task is to care about things and nurture them, make things better overall. It doesn't seem like they're ever going to do that, though.
They are sidelined, because giving a shit is not reflected in OKRs and giving a shit often equals standing in a way of "good enough" as judged by a middle manager and thus committing mortal sin of not focusing on getting to market faster.
If you are a metric driven organization, giving a shit is driven out of the organization in favor of tracked variables. Which usually happens around the time the company headcount hits Dunbar's number.
Do what they tell you, do the right thing for this immediate point in time right just now, don't do the right long-term thing!
eeuuuch, I feel horrible writing that even though I'm mocking it.
Ha! No, it doesn't. The moment that the capital owners can bisect responsibility enough that each cog can be replaced with an "equivalent" (read: younger/recently graduated, capable of typing code) cog, the smart and caring are discarded. This is because People With Opinions can derail the goals of the investors; because Smart People begin to understand just how pointless the ISOs are.
The founder with the engineering intelligence and the business intelligence to build their vision is the only on who stays stealthy and small, needn't take investors, needn't hire dozens of additional engineers.
The actual end result doesn't seem to matter too much, it's the time and cost savings that seem to be the motivators, pure ultra-short-term-ist capital-on-pedestal thinking, with barely a pause to consider 'the product'.
It's to the point now that I regularly see large and complex systems being built by essentially one guy but with dozens of "managers" overseeing his solo work. I've been in meetings with "project coordinators", "project managers", "governance", "change control managers", etc... all on the same single-product team and only one person there actually "presses the buttons".
This has shifted power and decision making away from the "smart people who give a shit" over to the "politicians that like to play Game of Thrones In The Workplace".
Look around you and see if you can spot more of these "inverted pyramids" with the point at the bottom: one technical person at the bottom "managed" by a team, which in turn has an even larger layer of managers above them, etc.
My (poor) understanding is that most have not received an actual explanation. It’s entirely possible some were cyberattacks.
2. The “smart” people at the top are generally selfish assholes. They abuse the system and others to self enrich. We don’t need more smart people, we need more caring people.
3. Nobody gives a shit anymore. The older generations fucked it up and are aging out and just saying haha sorry we messed it up but good luck while I chill in my 7th vacation home. The young are jaded because all the jobs are dogshit and underpaid. The only way to win is to get rich overnight on Kalshi or crypto or futures or whatever. Why would you work for most of these horrible companies? It’s not worth your life.
4. Look at POTUS. Grift on grift. Everything falls apart in a society that runs on grift. They couldn’t even re-line a pool…
It's kinda obvious then that smart people go for 2. It's just the logical conclusion.
I say that as someone who really wants to give a shit. After my first working experiences though I realized it is pointless.
there will come a moment when you are smart enough to know that you can screw over your boss or your neighbor with your intellect
then you have an entirely different problem: do you give a shit if the wrecking ball idiots get f-ed over and do you join in?
IMO, the issue is that AI is reducing the cost of building and modifying systems much faster than it's reducing the cost of understanding them. For example, an engineer can work on a problem or project for a week that could otherwise be done by AI in an hour or so. But, that week spent was not "wasted time"; it was understanding what it is they are building, discovering undocumented assumptions, knowing about different dependencies, developing intuitions about the system and how it works, etc.
This causes comprehension debt. Yes, the system does ultimately work, the tests also pass. But the level of comprehension goes down significantly.
That said, AI can also help reduce this debt by asking it what you need help understanding.
A good blog post on this: https://larsfaye.com/articles/ai-coding-will-prevent-experti...
And as far as air traffic is concerned, they’ve been trying to strangle it since at least 1980. Canada has a privatized system, so it’s possible to create such things but that is a matter of political will not money.
When you change a system directly you learn the underlying nature of the system and your toolset for making changes. Guide a third party toward making the changes and you learn the nature of the interaction and your toolset for evaluating the outcome of changes.
Does the distinction matter? Depends on your perspective I suppose.
Absolutely.
However, we've also never poured more in, to such centralised infrastructure.
I've actually never worked in any company that has had a communications outage for 36 hours in my life; and I've worked in places we had a dancer IRCd running on an old laptop under the faux floor in the server room with Solaris as the main communications tool... thing is: it was so simple, when it went down we just fixed it.
Technology companies have very successfully convinced us that we should outsource responsibility, because there are economies of scale. Then they ask for a free pass because "scalability is hard".
You don't get to say scalability is hard when you've been pushing and propagandising centralisation for over a decade, while having thousands of staff on million-dollar yearly TC packages.
Everyone here will say "nobody got fired for buying x- because everyone does" (Slack, IBM, Microsoft, AWS), and you can use it as an excuse... but you know what happens when we over-rely on something like that and it fails?
Economic crashes. That's exactly how the 2008 financial crisis happened, everything depending on something that had "absolved" responsibility. Such a thing has ruined the prospects of an entire generation of people, and I'm actually becoming really upset that we think we're being clever bastards because "oh hum, well, I can't be held responsible for total systematic collapse, everyone else was doing it!"
And yet, in the entire history of electromechanical switching in the Bell System, no central office was ever out of action for more than 30 minutes for any reason other than a natural disaster. (With one late exception, a major fire in New York City in 1975.[1])
That was achieved by design. Electromechanical telephone switches were designed to have no single point of failure. That was achieved in practice. Failures occurred all the time, but the problem was confined to a small group of lines, if not a single line. I'm not going to go into how that was done; read up on #5 crossbar if you're interested. Even complex functions such as long-distance routing had backdowns to static routes stored in read-only devices, in case the telco equivalent of BGP failed.
That reliability record has not continued into the computer era.
[1] https://en.wikipedia.org/wiki/1975_New_York_Telephone_exchan...