Legacycode01

479 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
479
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Legacycode01

  1. 1. Working effectively with legacy code 2010.12.23 geek—cafe, koduki - chapter 1 -
  2. 2. What is legacy code ?
  3. 3. not object oriented ?
  4. 4. NO
  5. 5. not beautiful ?
  6. 6. NO
  7. 7. nothing test ?
  8. 8. YES
  9. 9. If tests are written, an awful code is refactable. However, even a wonderful code is difficult change if there is no test.
  10. 10. 1. Changing Software.
  11. 11. Four reasons to change software <ul><li>Adding a feature
  12. 12. Fixing a bug
  13. 13. Refactoring
  14. 14. Optimizing </li></ul>
  15. 15. Change reason and type Adding a feature Fixing a bug Refactoring Optimizing Structure change change change New Function change Function change Resource change Test Code change Change
  16. 16. Points to change <ul><li>What should I change?
  17. 17. How can I confirm the change is correct ?
  18. 18. How can I confirm anything is not broken ? </li></ul>
  19. 19. These are very difficult. So we fear the change.
  20. 20. Risks by not changing <ul><li>the code becomes complex .
  21. 21. skill down for changing software.
  22. 22. fear of changing grows more and more . </li></ul>
  23. 23. To Be Continued Chapter 2.

×