Every decision we make in our projects has the potential to increase or reduce technical debt. While the only way to completely eliminate the debt is to never write any code, there are steps that we as engineers, project managers, and project stakeholders can take to mitigate our risk.

This talk covers the concept of technical debt, its potential to devastate projects, and red flags that project teams can look for to reduce its impact before it spirals out of control.


Comments are closed.

This presentation was both excellent and confusing at times. For example, I was a little confused by some of the examples such as what he referred to as a dependency and recipe-cpt.php, but maybe those make more sense to a Wordpress developer. However, I thought Steve did a nice job of explaining that technical debt is, when it is bad, and when it is good. I thought the idea of making documentation review a part of the code review process was a superb idea.