Getting Rid of Technical Debt

A presentation at G Adventures first Demo Night. Based off my blog post http://procrastinatingdev.com/programming/dealing-with-technical-debt/

Transcript

1. Getting Rid of Technical Debt
2. About Me @adammckerlie procrastinatingdev.com
3. Technical Debt: A debt that you incur everytime[sic] you avoid doing the right thing (like refactoring, removing duplication/redundancy) letting the code quality deteriorate over time. ! Martin Fowler
4. Take Inventory Use Google Analytics Understand Interactions Look Through Tests Create a Checklist
5. Have a Plan Coupled Functionality Does it need to be Refactored? Old/Unused Code
6. Create Realistic Timelines Talk to the Users Porting Old Data
7. Execute and Launch Small, Quick Iterations Tests Launch to Subset of Users
8. • Preventing Technical Debt Comprehensive Unit Tests Coding Standards Architecting for the Future
9. www.procrastinatingdev.com/programming/ dealing-with-technical-debt/ Read More At: