"I Worked for Block. Its A.I. Job Cuts Aren’t What They Seem."
https://www.nytimes.com/2026/03/04/opinion/block-jack-dorsey...
"Salesforce CEO says Block's cuts shouldn't fuel worries of mass layoffs: 'That company has its own unique issues'" https://www.aol.com/articles/salesforce-ceo-says-blocks-cuts...
one more :-) -
https://gizmodo.com/sam-altman-says-companies-are-ai-washing...
Sam Altman Says Companies Are ‘AI Washing’ Layoffs - https://gizmodo.com/sam-altman-says-companies-are-ai-washing... - February 21st, 2026
HN Search: AI Washing - https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...
Take block:
AFAICT, it was just really badly managed. A long time ago it got about as much share of its main market as it was going to get. They took the cash flow from that and hired a bunch more engineers to try to break into adjacent markets, and failed, and failed and failed.
Now they are just retreating to the steady income from their core business
They take in billions every year but still come away with millions in negative income. I have no idea what their problem is but I'm pretty sure the 1,600 people they just fired weren't it. Throwing away people in yet another round of layoffs to further invest in AI is not a good sign.
You see this with all manner of large enterprise in my experience, where what they continue to do is "good enough" to allow for these inefficiencies and actions because they are, on some spectrum, "money printers" due to their moat and inertia. Creative destruction is not a forgone conclusion, nor fast. Is the incumbent exploring the problem spaces adjacent to their core business(es) to increase their TAM to increase shareholder value? Are they innovating? Or are they just churning and burning up revenue on meaningless work?
All of these companies doing layoffs to invest in AI is not about AI specifically, it is about reaching for profits and yield in a challenging business landscape and macro post zero interest rate policy ("ZIRP") imho. They are desperate for productivity growth, whether that is doing more with less people, AI, offshoring, whatever because money now has a cost.
What actually happens is that company headcount grows based on how much money they make (or how much they raise), this justifies hiring more people. Then, structure is added, both to systems (eg. microservices), and to operations (eg. jira, workday, salesforce, etc) so that communication overhead doesn't grind everything to a halt. Then, once the business stops growing, headcount must shrink. This may take a long time, and it will be couched in all kinds of corporate bullshit to try to preserve morale and investor sentiment, but that is all window-dressing.
And as they say any new companies can replace the Atlassian products by bespoke vibe coded alternatives in a few days...
Our company has drastically downsized its dependence on Atlassian in the past month, we will be completely free in a few more. With the help of modern AI tools we've been able to replace their products with internal tools that are better tailored to our needs.
Why have every company vibe code their own semi-good bespoke tool when instead one company can handcraft the tool with optimisations much better than AI can ever dream of, and then sell that tool for a reasonable enough markup that the value proposition is big enough. Especially if the tool is open source open core, so companies can PR improvements they think will be broadly applicable.
You have never used an Atlassian product
Did they ever get around to fixing basic bugs like "Jira and Confluence use different markdown dialects"?
They've had a decade to address those sorts of obvious problems that bite 100% of the end users of their stuff, and apparently employed over 1600 people during that decade. That's 160 centuries of person time. I wonder what it was wasted on, if not making their fairly small core product suite usable.
I think we're going to see more and more incumbent companies with big moats and terrible products get replaced with vibe coded solutions over the next year or two.
It's easy to think of DIY software as "free" because you don't pay seat licenses, but DIY is expensive like a free yacht is expensive. It's a bottomless pit of money and time and upkeep.
Even if it's simple to implement, you still have to support it, update it, get people to use it, be on call if it tips over, teach people to use it, be forced to take it over when the person who wrote it leaves, etc, etc, etc
IT is a cost center and isn't staffed at the level of your revenue generator eng teams. You don't buy SaaS because you don't have other options, you buy SaaS to throw money at a vendor to take care of a problem for you, so your IT people can do the work you actually want them to do and not dick around rebuilding software that you already have.
That said, if you are a smaller company, you absolutely could kill Jira pretty quick.
Ticketing systems are not dumb CRUD apps, they're systems that build workflow engines. If you've never built a workflow engine, they're annoying but fine. Building an engine that can implement any special snowflake flavor of business workflow in a way that's reasonable with a reasonable UI is difficult.
And yes, you could write it for your special use case, but use cases change a lot and different groups need different use cases and the time you spend dicking around on building ticketing software that already exists is time you're not spending on shipping, and at the end of the day Jira is like $15/seat at sticker price, why are you bothering?
And that's why Jira is both terrible and still popular.
https://news.ycombinator.com/item?id=47343156 Atlassian to cut roughly 1,600 jobs in pivot to AI (reuters.com)
~yesterday, 273+ comments
An important update on our team https://news.ycombinator.com/item?id=47342835 - Yesterday, 18 comments
Does it matter if Atlassian is losing seat licenses because devs are being let go?
Back in the day we used Jira a lot. But we also had GitHub accounts. The integration of the two wasn't great so we switched to GitHub issues and kicked Jira to the curb. This saved money and also a lot of hassle in trying to keep the two in sync. I am wondering if many others went a similar route.
We did use Confluence and I do miss it. I would love to find an opensource replacement for it that stores files in markdown format. Like Obsidian, but for teams.