I think a lot of developers quietly share the same frustration—but we don’t say it out loud enough:
Deploying still feels harder than it should be.
Not because it’s impossible. Not because we lack the skills.
But because of everything around it.
- Too many decisions before you even start
- Too many moving parts for small projects
- Too much time configuring instead of building
- And somehow… still unclear pricing at the end
We’ve normalized this level of complexity as “just how things are.”
But the more I think about it, the less sense it makes.
Most of what we build isn’t at massive scale.
It’s:
- side projects
- MVPs
- internal tools
- quick ideas we want to test and ship
And yet the default experience often assumes we’re architecting something huge from day one.
That gap—that mismatch—is where most of the friction lives.
Good infrastructure, at least in my opinion, shouldn’t feel like a separate discipline you have to constantly manage. It should fade into the background and let you focus on what actually matters: building, iterating, and shipping.
The best tools are usually the ones you stop noticing.
They don’t slow you down.
They don’t make you second-guess decisions.
They just let you move.
And honestly, I think that’s the direction things are heading—whether slowly or not.
Less noise.
Less friction.
More building.
Top comments (0)