✳flâneur — a map of the web's best reading

Managing technical debt at an agile company

vadimkravcenko.com · 1,597 words · saved by 1 readers

Well this is a painful topic that haunts most companies in one way or another. Basically, technical debt is a what happens when you try to balance between what is needed now from the business perspective i.e. "We need this to start selling stuff and pay your salaries" and on the other side - what is needed from developers in the future to properly maintain the software, i.e. "proper tests, proper CI/CD". It's a hard thing to balance, and there's no silver bullet how to avoid it. In my opinion, the most important thing - it needs to be a conscious choice. Technical debt should never arise out of recklessness, it needs to either: As an agile agency, we build different kinds of software, we always keep in mind that software is a constantly evolving creature. Product owners always want new features to be added, infrastructure needs to scale, requirements change, people leave, knowledge gets lost, and needs refreshing. This is normal, each client has their own vision of the product that nee

Managing technical debt at an agile company vadim kravcenko development long-read startups teams Managing technical debt at an agile company 03 May 2021 · Updated 04 April 2026 Tuesday’s stand-up started with the same sentence from two different teams — “The build suddenly takes fifteen minutes, what changed?” Nothing changed, of course, except the invisible interest rate on the codebase finally came due. That’s technical debt in a nutshell: yesterday’s shortcut creeping into today’s velocity. The hard part is balance. On one side the business is yelling “Ship, we need revenue by Q3.” O

Explore this link on the map →

saved by

related reading