Most code gets read way more times than it gets written. That's another not necessarily value out activity if it's not easy to read. And this is that that's where there will be cruft within a code base of like somebody's written it with some kind of idiosyncrasies or some, you know, style of coding from way back. To me, it's a smart business decision to remove as much friction as possible so they can increase the value out activities that they're actually doing.
Technical debt has bounced into the spotlight after major system failures hit US aviation hard, forcing executive leaders to consider their own risk. Mike Mason and Rachel Laycock, Thoughtworks’ Global Heads of Technology and Enterprise Modernization, explore why addressing tech debt matters and how doing so can benefit your bottom line. If you are a business leader seeking practical ways to strategically manage your tech debt risk, this is the podcast for you.