The document discusses working with legacy code, describing it as old code that is difficult to maintain and test. It notes problems with legacy applications like difficulty adding features or introducing regressions due to changes. The document recommends following the Boy Scout Rule when working with legacy code, which is to leave the code cleaner than you found it. It provides contact information for the author to ask any questions.

1. Coding Dojo
Working on Legacy Code
Geek Time - September 2016
Nizar GARRACHE
OLBATI CTO

2. OLBATI - Geek Time - September 2016 2
Top Gear Kata
● git clone https://github.com/olbati/ocd-top-gear

3. OLBATI - Geek Time - September 2016 3
Legacy application...
● Generate revenue
● Are difficult to maintain

4. OLBATI - Geek Time - September 2016 4
What’s a legacy code?
● Old code base?
● Outdated technology
● “Legacy code is code without tests” - M. Feathers

5. OLBATI - Geek Time - September 2016 5
Problems with legacy application
● Nothing… if you don’t need to change it
● It’s hard to add new features
● Changes may introduce regressions
● Code hard to understand
● Can’t be delivered as quickly as you would like

6. OLBATI - Geek Time - September 2016 6
The Boy Scout Rule
Leave the campground cleaner than you found it

7. OLBATI - Geek Time - September 2016 7
Thanks!
Any questions?
@ngarrache
nizar.garrache@gmail.com