Featured Talk: Load JavaScript Faster by Steve Souders

Most Recent Talk: Virtual Interview… by Ralph Vituccio

Next Talk: Offering Your Con… by June Cohen & Others

Technical Debt - Refactor or Rewrite 4.2

Description:

Technical debt, a term coined by Ward Cunningham, is incurred by every project when the quick and easy route is taken to solve a problem. As technical debt builds up the problems of cruft begin to multiply. Development slows, bugs increase, deadlines are missed and frustration ensues. At chi.mp we incur technical debt just like any other development team. In this talk I’ll show you how we approach the reduction of our technical debt. Sometimes it makes sense to refactor existing code and sometimes it makes sense to start all over on certain parts of the code. In either case there are essential elements to successful technical debt reduction, including a solid understanding of the business requirements, a comprehensive test suite and both management and development teams that understand the importance of debt reduction. Ultimately, just like with reduction of financial debt, reducing your technical debt should leave you feeling satisfied and rejuvenated, ready to tackle future programming challenges.

Comments on this Talk

Missing brianshiro, 08 Oct 09:48

This user has yet to validate her/his profile with LinkedIn. It is therefore simple to assume that she/he is but a charlatan or common hoaxster. Mark as non-constructive

This talk really opened my eyes to the concept of technical debt. By giving it a name and explicitly dealing with the problem, we can try to manage it. Priceless advice for any organization.

Leave a Comment

Only SpeakerRate users can comment! Log in or Register.

6 Ratings: 4.2

Delivery: 4.35

Content: 4.05

Login or register to rate this talk!

Last Five Ratings

Welcome to the SpeakerRate Beta! Have feedback? Let us know over at Get Satisfaction (but be nice).