This document summarizes a workshop on rehabilitating legacy code. The workshop discusses that legacy code is inevitable and there are two main approaches to dealing with it - complete rebuilds or renovations. Rebuilding carries risks like underestimating time and costs and introducing new bugs. Renovation through refactoring in small, safe steps is recommended over botching changes. Techniques discussed include scratch refactoring, characterization tests, and telling the story of the system through sketches. The goal is to understand the impact of changes and improve the code in iterations.