April 11th 2019 15:00 - 15:20
I have been a part of teams where there is a lack of automated tests. The question of how to improve the code arises and one answer usually ends up being a rewrite. I have seen several rewrites and during these:
1) requirements/existing features are missed
2) they take longer than expected
3) new bugs are introduced
The rewrites have been proposed because the code is perceived to be too big/complex to get tests around it. So if rewrites are not the answer, what can we do?
Kaizen is the philosophy of continuous improvement of working practices. You decide to just make the code 1% better today instead of doing the rewrite. We will explore a three step process for improving the health of the code base through small, incremental, continuous improvement.