Upload
jenaiz
View
139
Download
2
Tags:
Embed Size (px)
Citation preview
–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”
good
better quality of the code
fast new features
no new features in a while
big release
new bug fixes
bad
good
50% new features / 50% code improvement
collisions between teams
bad/good code at the same time
bad
Broken windows theory http://en.wikipedia.org/wiki/Broken_windows_theory
–Robert Stephenson Smyth Baden-Powell (the father of scouting)
“Try and leave this world a little better than you found it”
good
There is no big bang release
Continuously improvements
Need cooperation/respect between people
No big change in the code
No big impact
bad
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
Reduce complexity within the scope of your task
Reuse functionality (DRY)
Test all the new features/bugs as much as you can
medium
Adapt yourself to the new requirements & Knowledge
Redesign part of your architecture
Do modularisation, reuse as much as you can
interesting
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