Go to the back of the room and . . .
Write down the biggest problem you've had with existing code: Put it on the left <=
Write down what you'd like to learn about dealing with existing code: Put it on the right =>
Legal case management
The difficulties it creates
Take a piece of code and refactor the hell out of it without trying to keep it working.
The goal is to explore the code and gain understanding, not to fix it (at least not yet)
To change something you must first understand it.
If you don't understand a piece of code, then how can you change it safely?
When the code makes you react like this:
Remove noise by spotting patterns:
Applying DDD while Scratch Refactoring
Figuring out what problem the code is solving
Scratch Refactoring Session
End of November
Topic: Scratch Refactoring Continued