> TL;DR I keep seeing the term "Technical Debt" used as some sort of justification for bad engineering: "we had to pick our battles", "it will be fixed when it's time", "it's what happens to all apps with...
> TL;DR If you see that teams "reject" the (part of) codebase, working with it lowers their engagement level, they have neither energy nor will to tackle its challenges, it's very rarely the matter of codebase's size. Sober-minded engineers just do not want...
Do you recognize any of the following scenarios? 1. Continuous influx of requirements put you into permanent death-march - you're always struggling against deadlines, there's never time for refactoring, unit testing, etc. 2. Firefighting is your bread'n'butter - issues pop up on...
Disclaimer: the idea of immutable code ain't mine - I've read/heard about it somewhere (can't recall precisely ;/) some time ago & it sticked with me. Code maintenance is already a huge problem & it won't get any better by itself. Software...
