Legacy Code is Fear @Swanseacon 08 09 2015
•Descargar como ODP, PDF•
3 recomendaciones•1,244 vistas
My talk "Legacy Code is Fear" at Swansea Conference http://swancon.co.uk in 2015
Recomendados
Recomendados
Más contenido relacionado
Más de Adi Bolboaca
Más de Adi Bolboaca (14)
Último
Último (20)
Legacy Code is Fear @Swanseacon 08 09 2015
- 1. Legacy Code is Fear www.mozaicworks.com
- 2. Me Adi Bolboacă Programmer Organizational & Technical Trainer & Coach www.mozaicworks.com
- 3. Legacy code scenario Current situation vs Better situation Not knowing what the actual code does Vs Gradually understanding the code and changing it to the minimum www.mozaicworks.com
- 4. Legacy code scenario Reasons why to change existing code: Fix a bug Add a feature Have automated tests for the system core www.mozaicworks.com
- 5. Legacy code scenario Reasons why not to change existing code: It looks ugly I would like to see nicer code I want to update to newest framework ... www.mozaicworks.com
- 6. Current situation You need to add some features to an existing old projectwww.mozaicworks.com
- 7. Current situation They tell you that you have a very short time to do it www.mozaicworks.com
- 8. Current situation You are afraid to change the system www.mozaicworks.com
- 9. Current situation The time feels waaaaay to short www.mozaicworks.com
- 10. Current situation And you tell your manager: I cannot do it www.mozaicworks.com
- 11. Current situation But the manager says... www.mozaicworks.com
- 12. Current situation It takes double the time you said www.mozaicworks.com
- 13. Current situation Your company loses money. Your customer loses money. www.mozaicworks.com
- 14. Current situation Everyone is stressed www.mozaicworks.com
- 15. Better situation Someone signs a contract to add some features to an existing old project www.mozaicworks.com
- 16. Better situation Your team starts writing characterization tests to understand the change www.mozaicworks.com
- 17. Better situation Your team writes end-to-end tests to understand the external dependencies www.mozaicworks.com
- 18. Better situation Your team splits the end-to-end tests into integration tests and unit tests www.mozaicworks.com
- 19. Better situation Your team starts adding more unit tests around the area that needs to be modified www.mozaicworks.com
- 20. Better situation Every member of the team is using the refactoring skills to improve the design www.mozaicworks.com
- 21. Better situation Your team adds the new feature. It is fully test automated. www.mozaicworks.com
- 22. Better situation Your testers make the final exploratory and manual tests www.mozaicworks.com
- 24. Better situation The team delivers on time. www.mozaicworks.com
- 25. Better situation Your company wins money and respect from your customer. Your customer wins money and has trust in you. www.mozaicworks.com
- 26. The problem: Legacy code is fear Our unknowns are making us afraid Automating tests minimizes the unknowns By automating tests we can increase confidence www.mozaicworks.com
- 27. Very nice But how to do this? www.mozaicworks.com
- 28. Find the known unknowns of the team Talk with the team Find what they do not know: domain knowledge, programming languages, unit testing, acceptance testing, frameworks, etc www.mozaicworks.com
- 29. Make small scale experiments Use a smaller problem at first Learn how to write charaterization tests for that problem Use coding dojos and mob programming to practice together www.mozaicworks.com
- 30. The littany against fear I must not fear. Fear is the mind-killer. Fear is the little-death that brings total obliteration. I will face my fear. I will permit it to pass over me and through me. And when it has gone past I will turn the inner eye to see its path. Where the fear has gone there will be nothing.... only I will remain Dune by Frank Herbert www.mozaicworks.com
- 31. Solve the legacy code fear: invest Invest in the future business agility of your company www.mozaicworks.com
- 32. Solve the legacy code fear: learn Find the unknowns of the team Make a medium-term learning program Make small scale experiments Learn Extend to bigger scale experiments Learn Do a small change request in production Learn www.mozaicworks.com
- 33. What's next? Read the Working Effectively with Legacy code book by Michael Feathers Find a good trainer to help the team learn Build learning program with team&trainer Learn from each experience Check blog.adrianbolboaca.ro www.mozaicworks.com
- 35. Thank you! Check my work on blog.adrianbolboaca.ro (articles and code casts) www.mozaicworks.com See the slides at http://www.slideshare.net/adibolb
- 36. Extend your mentoring & training capacity Accelerate learning through communities of practice Grow your functional leaders and top talents http://www.mozaicworks.com adrian.bolboaca@mozaicworks.com @adibolb