How to face legacy projects

Qualquer profissional é capaz de deixar seu legado no lugar onde atua, e no universo da tecnologia da informação não é diferente. Dia-a-dia termos o desafio de manter aplicações que possuem uma estrutura que não foi definida por nós mas que devem ser sustentáveis para os envolvidos. Nessa talk entenda como uma aplicação legado pode influenciar negativamente a saude do projeto e como previnir esse tipo de comportamento para que projeto legado não seja um problema e continue sendo solução.

Transcript

1. How to face Legacy Projects Learn what to do when legacy codes become an enemy of the project
4. GO HORSE, BABY!
6. PERFECT MOMENTS FOR MISTAKES
8. IS IT TIME TO REMAKE?
9. NO
10. MONSTERS DON'T NEED TO BE DESTROYED, THEY NEED TO BE CONTROLLED
11. Definitions of legacy codes • Legacy code is source code that relates to a no-longer supported or manufactured operating system or other computer technology. • All Code Is Legacy Code. • A legacy code is a undocumented or untested code that doesn't have any quality assurance and understanding.
13. ALWAYS HAPPEN BECAUSE IT'S EASY
14. Let's Talk about TIPS
15. • Your time is a box • Make sure your task is compatible #1 - Know how to use your time
16. #2 - Let's monitoring • Sonarqube - Code Quality and Security • Elasticsearch - APM Server • Refactoring based on feeling is a risk
17. #3 - Test cases are welcome Your implementation needs to be solid and the tests will be ensure the other parts of the system keep working.
18. #4 - Make Patterns your best friends Patterns are important to keep the consistency and understanding of the project. • Repository Pattern • Singleton Pattern • Factory Pattern • S.O.L.I.D • Linter's
19. #5 - Learn to say "NO" Some time it's important to be incisive and to say "no" to some tasks.
20. #6 - Have a Good Communication Keep your team, your leader and customer known about your decisions. Bring exemples, other perspectives to solution the problem. You need to be simple, transparent and honest with the project and yourself.
21. Be careful and try to avoid...
22. Rigidity Changes are not welcome because all the system is impact because them.
23. Fragility Changes affect parts of the system where conceptually they shouldn't
24. Immobility So hard separate modules in the system.
25. Viscosity To do the right is more difficult than wrong.
26. Unnecessary Complexity To do something that don't increase a direct benefit.
27. Unnecessary Repetition Copy and paste is not a good choice.
28. Opacity The motive of the project is not clean. It is confused and incomprehensible.
29. You need to know: your choices will be result in Technical debt
30. Technical Debt • This is a debt that is assumed when choosing a design or an easy approach in the short time but with a negative impact on the long time. • “A dívida técnica é similar à dívida financeira. Assim como a dívida financeira, a dívida técnica exige o pagamento de juros. Estes vêm na forma de esforço extra, que devem ser pagos em desenvolvimentos futuros por conta da escolha de um design mais rápido e de baixa qualidade." (Martin Fowler)
31. The perfection is an enemy for what's razonable good.
32. Focus on create a good communication with the stakeholders .
33. Your job is decrease real risks for your customer.
34. We work for people because people.
35. Thank you