Any developer who has ever taken over a codebase or come in on a large project is familiar with it: technical debt. Code written years ago, serving no clear purpose. But... Remove the code, and everything falls apart. With a bit of bad luck, you may not even be able to edit it safely.

How do you deal with this? In this talk, we look at ways to identify how big the problem actually is, and possible solutions. How do you tackle a codebase that has become so big that you get lost?