Quality with purpose
There’s an argument to be made that code quality doesn’t really matter. What matters is shipping fast, and you an sort everything else out later.
I get that, but don’t buy it. Many of us have worked on projects that are soul-crushingly painful to work on because the code is crap.
But… quality isn’t always good, either.
One thing I’ve been thinking about recently is applying quality to the right things.
The best microservices in the world are actually bad if what you need is a monolith.
The perfect abstraction is pointless if your approach is all wrong.
Doing great work matters a lot. But you have to pair that with working on the right things.