Ok, I think Matt’s goofy for various reasons. From just what this article says, I think he’s right on this one. This is my understanding of it:
* The dev team has a disagreement about putting one of the company’s own projects on the available plugins carousel or whatever inside their main product.
* They eventually decide not to.
* The CEO says “this has been an important part of our product for 20 years. It’s silly that we’re even debating this”, and put it there anyway.
And that’s about it? Based only on what I read here, there wasn’t any compelling engineering reason not to do a thing, and the CEO made a product decision to do it. That sounds like something I’ve heard 1,000 times at different shops and I’m not sure what the problem is.
Perhaps I’m misreading this, and the main point isn’t “CEO overrides valiant dev team”, but “CEO makes recalcitrant dev team stop bikeshedding”.
I say this out of no love for Matt’s… “interesting”… decision making the last couple of years. This sounds reasonable to me though.
Leaving out the optics and personalities and internal politics, the biggest issue I see is that they added this during the RC phase, which is against their policy. It should have been pushed to 7.1.
> Business objectives should override engineering policies when the two are in conflict
This is an excellent way to get stuck with only the engineers sucky enough to have to put up with that, which is not the norm.
However, in this specific case, it looks like engineers were making a product decision, not an engineering one, and management decided to make a different product decision. That feels categorically different than "mauve has more RAM".
> most software development is not "real engineering".
Most software development doesn't have anywhere near the real world impact of the Boeing/NASA engineering you reference.
Good engineering practice recognizes the risks and scales the effort to match it.
A CRUD app for internal users has a different set of requirements than a revenue generating SaaS app, just like a backyard fence has different building criteria than a highway bridge.
It says a lot about what's been going on in the Wordpress ecosystem lately that I had never heard of Mullenweg before maybe a year or two ago, and now I immediately see his name and think "What's he done this time?" Probably very frustrating for many people who actually use the platform, but as someone who doesn't, it's almost morbidly fascinating watching the continued drama and wondering if and when any of it ends up hurting the bottom line enough that something changes. I've joked to my wife before that if they end to running into issues and sell Tumblr, and it follows the trend of how much cheaper it was the second time, it might mean we could just buy it ourselves and run it.
Same here. I had no idea who he was before the WP Engine debacle. He’s been fascinating to watch for someone who enjoys the occasional low stakes, high drama public spat.
But what did he do this time, though? I don't understand it very well, but it sounds like they made an anti-spam solution the default? That is good, right? WP gets a lot of spam.
It introduces a new prominent page in your wordpress settings that recommends popular services to you. All other services are behind a link that says "Find more connectors in the plugin directory" and are less visible.
People on the Internet are just so dramatic. "Terrifying". Yes, indeed, this induces "terror", abject fear. Give me a break. At worst it's slightly cringe-worthy. This treadmill of dysphemisms is honestly annoying. At this point, all actions are described in extreme terms as if they're life changing when they're only mildly quirky.
I guess I'm confused about Matt wanting to "right the ship" so to speak, while also shoving this through. (Idgaf, it's a product call ultimately)
But it seems the clean, sustainable, long-term way to do this was to have the akismet plugin simply self-register. Why was this hack easier than just doing that?
Ok, I think Matt’s goofy for various reasons. From just what this article says, I think he’s right on this one. This is my understanding of it:
* The dev team has a disagreement about putting one of the company’s own projects on the available plugins carousel or whatever inside their main product.
* They eventually decide not to.
* The CEO says “this has been an important part of our product for 20 years. It’s silly that we’re even debating this”, and put it there anyway.
And that’s about it? Based only on what I read here, there wasn’t any compelling engineering reason not to do a thing, and the CEO made a product decision to do it. That sounds like something I’ve heard 1,000 times at different shops and I’m not sure what the problem is.
Perhaps I’m misreading this, and the main point isn’t “CEO overrides valiant dev team”, but “CEO makes recalcitrant dev team stop bikeshedding”.
I say this out of no love for Matt’s… “interesting”… decision making the last couple of years. This sounds reasonable to me though.
Leaving out the optics and personalities and internal politics, the biggest issue I see is that they added this during the RC phase, which is against their policy. It should have been pushed to 7.1.
Business objectives should override engineering policies when the two are in conflict, at least if you're a business owner who wants to make money.
> Business objectives should override engineering policies when the two are in conflict
This is an excellent way to get stuck with only the engineers sucky enough to have to put up with that, which is not the norm.
However, in this specific case, it looks like engineers were making a product decision, not an engineering one, and management decided to make a different product decision. That feels categorically different than "mauve has more RAM".
>Business objectives should override engineering policies when the two are in conflict, at least if you're a business owner who wants to make money.
This bush league kind of attitude is why people insinuate that most software development is not "real engineering".
When Boeing or NASA lets making money get in the way of good engineering practice, people die.
> most software development is not "real engineering".
Most software development doesn't have anywhere near the real world impact of the Boeing/NASA engineering you reference.
Good engineering practice recognizes the risks and scales the effort to match it.
A CRUD app for internal users has a different set of requirements than a revenue generating SaaS app, just like a backyard fence has different building criteria than a highway bridge.
"died in a blogging accident"
It says a lot about what's been going on in the Wordpress ecosystem lately that I had never heard of Mullenweg before maybe a year or two ago, and now I immediately see his name and think "What's he done this time?" Probably very frustrating for many people who actually use the platform, but as someone who doesn't, it's almost morbidly fascinating watching the continued drama and wondering if and when any of it ends up hurting the bottom line enough that something changes. I've joked to my wife before that if they end to running into issues and sell Tumblr, and it follows the trend of how much cheaper it was the second time, it might mean we could just buy it ourselves and run it.
Same here. I had no idea who he was before the WP Engine debacle. He’s been fascinating to watch for someone who enjoys the occasional low stakes, high drama public spat.
But what did he do this time, though? I don't understand it very well, but it sounds like they made an anti-spam solution the default? That is good, right? WP gets a lot of spam.
Akismet makes money for Automattic / Matt.
Comment spam is terrible and will continue to get worse.
Decent alternatives exist.
Increasing the visibility of Akismet should help increase revenue.
This is 100% a financial move.
What is a "connector" in this context?
The Connectors API is a framework for managing connections to services like AI, anti-spam, etc. It was introduced on March 18, 2026 with WordPress 7.0 at https://make.wordpress.org/core/2026/03/18/introducing-the-c...
It introduces a new prominent page in your wordpress settings that recommends popular services to you. All other services are behind a link that says "Find more connectors in the plugin directory" and are less visible.
See image https://developer.wordpress.org/news/files/2026/03/image-1.j..., which is the second image on "What’s new for developers?" at https://developer.wordpress.org/news/2026/03/whats-new-for-d...
>Automattic-sponsored core committer Jorge Costa
>Fueled-sponsored core committer Peter Wilson
>Bluehost-sponsored core committer Jonathan Desrosiers
>Human Made-sponsored core committer John Blackbourn
This is a terrifying way to describe people.
It does make the implicit explicit though, right? Each of these folks have a personal viewpoint but also represent a corporate viewpoint.
Why? People are referred to as committers everywhere. I like the transparency and credit this gives to the ecosystem users helping fund development.
When I did OSS work paid for by my employer, I was careful to note and credit who paid for the PR.
People on the Internet are just so dramatic. "Terrifying". Yes, indeed, this induces "terror", abject fear. Give me a break. At worst it's slightly cringe-worthy. This treadmill of dysphemisms is honestly annoying. At this point, all actions are described in extreme terms as if they're life changing when they're only mildly quirky.
I guess I'm confused about Matt wanting to "right the ship" so to speak, while also shoving this through. (Idgaf, it's a product call ultimately)
But it seems the clean, sustainable, long-term way to do this was to have the akismet plugin simply self-register. Why was this hack easier than just doing that?