Contenu connexe Plus de Gunnar Peipman (9) Working with legacy code2. About me
Name: Gunnar Peipman
Job: Chief Everything Officer
Company: Peipman Consult Ltd
Hobbies: Coding, reading, travelling, beers
In family: boyfriend, step father and father
Animals: white fluffy bunny
Me & MS: ASP.NET/IIS MVP, blogger, speaker
Community: ENETA (www.eneta.ee)
http://weblogs.asp.net/gunnarpeipman/
E-mail: me@gunnarpeipman.com
3. Agenda
What is legacy code and where it comes from?
How to fight back?
Tools and techniques
Examples
Questions and answers
5. What is legacy code?
The code we already released to users
Code covered with no tests
Messy code
7. Where legacy code comes from?
Death march projects
Unskilled developers
Impossible dead-lines
Bleeding-edge technologies
Complex technologies
Silver-bullet tools
Digital slavery
8. Dynamics of legacy code
All problems happen every day with
small steps under our own eyes
10. How to fight back?
Write readable code
Write testable code
Refactor
Avoid hacks
Look how others have solved similar problems
Study different patterns
Improve your coding skills
If you find mess then clean it up
15. Patterns
Design patterns
Unit testing patterns
Analysis patterns
Enterprise applications architecture patterns
Enterprise integration patterns
SOA patterns
Universal data models
16. Testing
Unit tests
Integration tests
Stress tests
Performance tests
User Interface tests
Database tests
Acceptance tests
Tracer bullet tests