15
Forget technical debt
(www.ufried.com)
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
As a lead dev I have plenty of cases where I weigh effort vs impact and risk and conclude to "this is good enough for now". Such cases are not poor management - which I assume you mean something like "we have to ship more faster, so do the shortest". Sometimes cutting corners is the correct and good decision, sometimes the only feasible one, as long as you're aware and weigh risks and consequences.
We, and specifically I, do plenty of improvements where possible and reasonable. Whatever I visit, depending on how much effort it is. But sometimes effort is too much to be resolvable or investable.
For context, I'm working on a project that has been running for 20 years.
In this context, YAGNI is a very good principle, because incidentally, working too much ahead to avoid technical debt can actually cause technical debt.