The art of deleting code by Claudio Baccigalupo As the size of your project grows, some blocks of code become irrelevant. How can you find and delete them? And how can you be sure code is actually dead? This talk will review a few techniques I learned from removing 50,000 lines of Ruby code at work. We will see how git can help, with commands like blame, log --follow, and bisect. We will talk about static analysis, and running code coverage in development. We will explain how Ruby meta-programming can conflict with the "Find in Project" approach. We will show how to be nice to reviewers when submitting Pull Requests that delete code.