If you’ve ever wondered how to make smarter trade-offs between shipping now and scaling later, this one’s for you.
In my experience, most individual programers have a reasonable relationship fast development and technical debt.
It's management structures that incentivize middle management to enforce fast releases cadences, with no care over the quality of the releases, that have really failed us.
I'd love to see some advice on how to deal with quantity-over-quality management styles.