2 ms·
Tech debt should be concious Engineering trade offs made for some business benefit. Tech mess is on the other hand just messy code. Rewrites are rarely the be
by quickthrower2 4y ago
Tech debt should be concious Engineering trade offs made for some business benefit.
Tech mess is on the other hand just messy code.
Rewrites are rarely the best solution for either. Especially for a product that pretty much works and has paying users.
- dragonwriter 4y ago> Tech debt should be concious Engineering trade offs made for some business benefit. Tech mess is on the other hand just messy code. > Tech mess is on the other hand just messy code. Not having coding standards, code reviews, and time allocated to refactoring for code health built in are all choices, made based on management business priorities. They may be poorly informed choices, but that’s true of the choices that result in traditional financial debt, too. Distinguishing between well-considered tech debt and poorly-considered tech debt is certainly meaningful when you are discussing the management processes involved, but narrowing “tech debt” to the well-considered is unjustified, and blurs the fact that the impact once it exists is the same no matter whether the trade-off was worthwhile or even thought through that resulted in it.