Skip to content

Just Use Postgres as a Queue?

I’ve noticed a trend, and a lot of people are saying the same thing: just use Postgres as a queue. No Kafka, no Redis, no RabbitMQ, just one database for everything. And I totally get it. I get the appeal. There are fewer moving parts. There is less infrastructure. There is only one thing to run. But what feels simple at the very beginning can often lead to a lot of complexity later. It’s like using Excel when you really need a database. Sure, it holds data. You understand Excel well. But are you really about to build a relational… Read More »Just Use Postgres as a Queue?

Testing Needs a Seam, Not an Interface

In my last video, I said that clean architecture was killing your velocity. And man, you guys had thoughts. The number one pushback, the hill a lot of people were willing to die on, was testing. And I get it. On the surface, it sounds reasonable. Create some interface or abstraction for testing purposes. But that assumption starts to fall apart once you look at what testing actually needs. Testing needs a seam. It does not automatically need an interface. YouTube Check out my YouTube channel, where I post all kinds of content on Software Architecture & Design, including this video showing… Read More »Testing Needs a Seam, Not an Interface

Why “Clean Code” is Killing Your Velocity

We’ve been told that clean code and deadlines are opposites. That if you want to ship fast, you have to write garbage code full of hacks. But if you want to get it right, you need to add boilerplate. That’s a lie. Here’s the thing: a lot of the so-called best practices people tell you to follow are a scam. Adding layers, interfaces, and abstractions does not automatically help you ship faster. That is not architecture. A lot of the time, it’s just liability. YouTube Check out my YouTube channel, where I post all kinds of content on Software Architecture & Design,… Read More »Why “Clean Code” is Killing Your Velocity