Adam Tornhill is a programmer who combines degrees in engineering and psychology. He’s the founder of CodeScene where he designs tools for code analysis. Adam is also the author of multiple technical books, including the best selling Your Code as a Crime Scene and Software Design X-Rays. Adam’s other interests include modern history, music, retro computing, and martial arts.
Prioritizing technical debt is a hard problem as modern systems might have millions of lines of code and multiple development teams — no one has a holistic overview. In addition, there's always a trade-off between improving existing code versus adding new features so we need to use our time wisely. What if we could mine the collective intelligence of all contributing programmers and start making decisions based on information from how the organization actually works with the code?
Effective software development requires that we keep code and people in balance so that one supports the other. Yet, this equilibrium often eludes us, leading to coordination challenges, tightly interconnected services, and fragile code which is painful to change.Such challenges stem from the fact that the organization which builds the system is invisible in the code itself. Without a clear view of this social dimension, we're left grappling with surface-level fixes rather than addressing the root causes. What if we could visualize this intersection of code and people?