Man seems to insist on ignoring the lessons available from history.
Chapter 1Why Technical Debt Isn’t Technical
Most organizations find it hard to prioritize and repay their technical debt because of the scale of their systems, with millions of lines of code and multiple development teams. In that context, no one has a holistic overview. So what if we could mine the collective intelligence of all contributing programmers and make decisions based on data from how the organization actually works with the code?
In this chapter you’ll learn one such approach with the potential to change how we view software systems. This chapter gives you the foundation for the rest of the book as you see how behavioral code analysis fills an important ...
Get Software Design X-Rays now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
