z2018 notes Cutting Legacy Code Quickly

Based on the workshop at Coders Only by @LlewellynFalco

@ollispieps, @crashtester

Refactoring Kata examples

Good examples to practice your skills can be found on Github:

• GildedRose Kata @ GitHub
• GildedRose Refactoring Kata @ GitHub

Approvals Testing

• Approvals Project @ GitHub
• ApprovalTests.Java
• Video: Using ApprovalTests in Java

Clear commit messages

Arlo's Commit Notation: https://github.com/RefactoringCombos/ArlosCommitNotation

• Video: Arlo's Talk at Craft Conf 2018

Prefix	Meaning
F	Feature
B	Bug
!!!	non-provable refactoring
c	comments (add/delete)
d	developer documentation changes (not end-user facing)
e	environment (non-code) changes
t	Test only
r	Provable Refactoring
a	Automated formatting

Key: lower case means low risk.

Provable Refactorings

A collection of refactoring recipes that are provably safe. They never accidentally introduce nor fix a bug, including one that you don't know exists. They maintain all behavior, including unknown or unspecified behavior. To accomplish this, each recipe is concrete and language-specific.

• Provable Refactorings: https://github.com/InnovatingTeams/provable-refactorings

Branch Normalisation

@crashtester came with the name "Branch Normalisation" for what @LlewellynFalco showed us at Coders Only.