Uncategorized

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

What’s overengineering? Is the outbox pattern, CQRS, and event sourcing overengineering? Some would say yes. The issue is: what’s your definition? Because if you have that wrong, then you’re making the wrong trade offs. YouTube Check out my YouTube channel, where I post all kinds of content on Software Architecture & Design, including this video showing everything in this post. “The outbox pattern is only used in finance applications where consistency is a must. Otherwise, it’s just overengineering.” Not exactly. “CQRS is overengineering and rarely used even at very high scale companies. One master DB for writes and a bunch of replica… Read More »Read Replicas Are NOT CQRS (Stop Confusing This)

You have some code that handles placing an order. This could be an HTTP API or a message handler. You made it idempotent. You added a unique constraint on some kind of message ID. And somehow… you still end up double charging the customer’s credit card. YouTube Check out my YouTube channel, where I post all kinds of content on Software Architecture & Design, including this video showing everything in this post. Idempotent You did everything right. You have idempotency. You have an inbox table and a unique constraint on that message ID. Your handler should be exactly once, right? Wrong. And… Read More »Your Idempotent Code Is Lying To You