Monday October 20, 2014, 8:30am - 5pm
Location: SPLASH '14 Conference in Portland
This is the website for the SPLASH workshop on
Technical debt is a term that was coined by Ward Cunningham in 1992 to explain the accidental complexity that is a side-effects of "going faster" in the development work on a large code base.
Technical debt is a popular and powerful metaphor for small teams, projects with very short development cycles, and teams working in agile ecosystems, but it can apply to development projects of any size or circumstances.
This workshop examined the sources of technical debt, especially in the world of big software engineering. What are the best practices for keeping technical debt under control? The workshop participants shared both academic and industrial experiences.
This workshop has some overlap with the SPLASH 2013 workshop on technical debt (see SPLASH 2013 technical debt workshop report for more information on what we discussed).
Too late... the workshop has already been held. But you can read the workshop final report:
Some of the questions we asked before the workshop...
What are your experiences in dealing with technical debt? You can join in on the discussion. Here is how you can become part of the workshop:
Extra material (useful readings, links to books and articles on technical debt issues) will be posted here.