Many software systems contain code that is overly complicated, hard to understand, and hence expensive to change and evolve. Prioritizing technical debt is a hard problem as modern systems might have millions of lines of code and multiple development teams, so no-one has a holistic overview. In addition, there is …
You often hear technical debt described as a personal failure for software developers of the Scrum team. Why didn’t you code with greater rigor? By creating technical debt, how could you have made life harder on people working in the code? More often than not, technical debt is the result …
Technical debt is a natural byproduct of every successful software system. Great teams learn how to use technical debt to their advantage to improve time to market and balance short-term gains with long term pains. This talk shares some experiences creating, measuring, and paying down technical debt by sharing how …
This talk discusses technical debt, the code quality factors, the SonarQube’s core ideas and its main features that simplify the process of tracking and improving software quality.
At the SATURN 2014 conference, Jeromy Carrière of Google, Philippe Kruchten of the University of British Columbia, Robert L. Nord of the Carnegie Mellon Software Engineering Institute, Michael Keeling of IBM and Rebecca Wirfs-Brock discuss about technical debt. The discussion is moderated by George Fairbanks of Google.
Cruft is inevitable. Whether you’re working around a bug in Internet Explorer, Heroku or Ruby 1.8, our libraries and applications quickly diverge from the platonic ideal of software. In the short-term, there’s no point in fretting. Rather than an indication of a development process gone awry, the technical debt merely …
