It’s a cynical way to view the C-staff of a company. I think it’s also inaccurate: from my limited experience, the people who run large tech companies really do want to deliver good software to users.

From my much broader experience, this is missing the required cynicism that C-staff want to deliver software they think is good based on the criteria cynical yes staff tell them constantly is good. I’ve never met an exec that didn’t want to deliver something good; most execs I’ve met don’t actually understand what good is or how to benefit people.

This isn’t recent. This has been an ongoing thing for at least 20 years (if not longer; that’s just the earliest I remember having this convo). Yes, it cleans the wound by killing things but it also fucks up the healthy tissue around the wound (see other comments for a more scientific explanation). Having some in a medical kit is useful for other activities such as diluting with water for an ear rinse, diluting with water for various mouth stuff (rinse not swallow), and some skin treatments (again, diluting first).

$2/mo is pretty close to what Reddit premium was back before they turned the Reddit silver meme into a real thing! That’s a great amount to donate. Don’t sell yourself short.

Monoliths are the answer to bad microservices. Microservices are the answer to bad monoliths. It’s all cyclic and four different architects are going to have fifteen different opinions on how your system should be built. Do the thing that makes sense for your team and try to stay flexible.

Absolutes in programming tend to lead to bad designs. This is more a “I’m gonna stir up some shit on Twitter” post than real wisdom.

• No microservices usually leads to bloated, tightly coupled logic that ignores business domains
• No monoliths usually leads to sprawling microservice deployments with tightly coupled dependencies and flavor-of-the-week new ones
• No Kubernetes usually leads to VPS pets or crazy obstacle courses trying to get SSL termination without a million fucking dependencies in a cloud container orchestration system that isn’t as good as Kubernetes
• All Kubernetes usually leads to huge SRE costs for a tiny app

The same shit happened last summer when AWS came out with their “we dropped microservices for a monolith and look at our speed increase” article which ignored good design principles. Sometimes you should split things over business domains so you can deploy and code independently. Sometimes Kubernetes is the best way to handle your scale needs. The stories we normally read are about people doing it wrong (eg AWS making a bunch of microservices inside a domain sending fucking gigs of data between what should have been functions in a single service). Inexperienced folks don’t always know when to move from their minimum viable solution to something that can scale. That doesn’t mean you remove these things, it means you train on when you need them.

Should we abandon design patterns because singletons or flywheels aren’t the correct solution all of the time?