We all talk about “moving fast” and “shipping features,” but who picks up the tab for those shortcuts? In Part 2 of our series on Technical Debt vs. Technical Assets, we tackle the pushback head-on:
• Why the true “lender” is your future self—and every developer (and stakeholder) who follows
• How calling it “debt” sparks the urgency executives and engineers need to act
• Why every asset carries upkeep costs—and how to keep your investments healthy
If you’ve ever wondered how to make smarter trade-offs between shipping now and scaling later, this one’s for you.
dlcarrier•3h ago
Thanks for addressing this. The amount of boost added on to of bloat from most corporate software developers really does make life more difficult, for everyone.
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.
mbastos•5h ago
If you’ve ever wondered how to make smarter trade-offs between shipping now and scaling later, this one’s for you.
dlcarrier•3h ago
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.