Agile retrospective - Battleship
A new way to do retrospectives
A new way to do retrospectives
Data abstraction and hierarchy
Bypass the ‘Open class’ problem
Code should be extended not modified
Code should only have one reason to change
Running through sets of data
Choose which way to go
Saving some typing (Git aliases are so 2015…)
Faster dev, happier dev
Contract implementation