Build vs Buy: Why the Best Side Projects Are Boring

The Most Dangerous Lie in Indie Development

There's a quiet arrogance that sneaks into every developer's mind at some point: *I can build that myself.* It feels like strength. It's actually a tax on your time.

The best indie developers I know have one trait in common — they're weirdly excited about boring technology. Feature flags? "Install Microsoft.FeatureManagement, put some flags in appsettings.json, and you're off to the races." That sentence isn't inspiration. It's a warning shot across the bow of anyone about to spend three weeks building their own experimentation framework.

What Changed

AI tools have made writing code cheaper than ever. That sounds empowering. The opposite is true. When the marginal cost of writing a module drops to near zero, the temptation to reinvent rises proportionally. You *can* build a better authentication system. You *can* fork a CMS and customize it. You *can* write your own notification engine.

The question isn't whether you can. It's whether you should.

I've watched brilliant developers spend months shipping something "better" only to discover ten competitors already had working products. None of them were mocking themselves — they genuinely couldn't see the trap until they fell in.

A Simple Decision Framework

Before writing a single line, ask three questions:

1. Does an open-source library solve 80% of this? If yes, use it.
2. Would a SaaS product solve it for less than your hourly rate? If yes, pay it.
3. What is the actual differentiating value my custom build provides? If you can't articulate this clearly, you don't have a reason to build.

Most projects fail the third test. That doesn't make them bad ideas — it makes them the wrong investment of your most scarce resource: time.

The Real Asset

Your code is not valuable. Your *judgment about what not to code* is.

Every hour spent maintaining a homegrown solution is an hour not spent on the feature your users actually want. Every dependency you refuse to adopt because you wanted "full control" is a debt you're taking on for pride, not product-market fit.

I learned this the hard way. Three months building a dashboard. Ten products existed. Mine was slower, uglier, and mine alone. The other nine had customers.

Now my rule is simple: buy first, use second, build only when there's no alternative. This rule has saved me more than it has cost. The products that survive aren't the ones with the cleanest internal architecture. They're the ones that shipped something people wanted before the founder burned out trying to be clever.

Boring wins. Always.