Technical debt is something that you should take care about. In this talk I have introduced the problem and the solution to that. Trying to show what is the choices that we have and that we can apply. My favourite, The boy Scout technic.

1. Refactoring as a Boy Scout
by Jesús Navarrete (@jenaiz)
(HRS Holidays - Tech Talk)

2. What is the problem?

3. new features ,, fix bugs ,, knowledge ,, humans

4. fast, fast, fast

5. Laziness is contagious

6. … vitality too!

7. What is technical
debt?

8. –Actively Lazy blog
http://blog.activelylazy.co.uk/tag/technical-debt/
“Technical debt is simply an inability to quickly
make changes to an existing system”

9. … do we have options?

10. Big Bang
Dedicated Tasks
Boy Scouts

11. ...what about Big
Bang...

12. good
better quality of the code
fast new features
no new features in a while
big release
new bug fixes
bad

13. ...what about
Dedicated Tasks...

14. good
50% new features / 50% code
improvement
collisions between teams
bad/good code at the same time
bad

15. ...the last one… The
Boy Scout rule

17. Broken windows theory
http://en.wikipedia.org/wiki/Broken_windows_theory

18. –Robert Stephenson Smyth Baden-Powell (the father of scouting)
“Try and leave this world a little better than you
found it”

19. –Martin Fowler
“Leave your code better than you found it”

20. good
There is no big bang release
Continuously improvements
Need cooperation/respect
between people
No big change in the code
No big impact
bad

21. … what you should do
IMHO...

22. Remove commented code before commit
Remove unused code or unused objects, clean
Write a good commit message
Rename names difficult to understand
Define the right visibility for your methods
small

23. Reduce complexity within the scope of your task
Reuse functionality (DRY)
Test all the new features/bugs as much as you can
medium

24. Adapt yourself to the new requirements & Knowledge
Redesign part of your architecture
Do modularisation, reuse as much as you can
interesting

25. … sometimes is difficult
to see that you have
problems...

26. Thx! Q?

27. References…
• 97 Things Every Programmer Should Know, by “…”
• Clean Code, by “Uncle Bob”
• http://programmer.97things.oreilly.com/wiki/index.php/
The_Boy_Scout_Rule
• http://en.wikipedia.org/wiki/Broken_windows_theory
• http://en.wikipedia.org/wiki/Technical_debt
• http://martinfowler.com/bliki/TechnicalDebt.html