Here are all the presentations I received, organized by day:
Monday, April 18: DagstuhlMTD_Day1
Tuesday, April 19: Dagstuhl-MTD-Day2
Wednedsday, April 20: Dagstuhl-MTD-Day3
Thursday, April 21: Dagstuhl-MTD-Day4
Here are the slides presented during my lightening talk :
Remediations in SQALE-Dagstuhl
In software-intensive systems, technical debt is a design or implementation construct that is expedient in the short term, but sets up a technical context that can make a future change more costly or impossible. Technical debt is a contingent liability whose impact is limited to internal system qualities, primarily maintainability and evolvability.
As requested, the definition that Ipek presented is below. Feel free to refute, extend, show gaps, etc. in the comments so we can improve:
Technical debt as a software design issue that:
And last, but not least, thanks a lot to our colleagues from Brazil (Graziela Tonin, Fabio Queda Bueno da Silva, Alfredo Goldman, Guilherme Horta Travassos) for treating us all to such a fun, cultural classic from their part of the world. In case next week you would like to try this yourselves here is the recipe:
Ingredients: Half a lime cut into 4 wedges, 2 Teaspoons brown sugar, 1 2/3 oz Cachaça
Preparation: Place lime and sugar into old fashioned glass and muddle (mash the two ingredients together using a muddler or a wooden spoon). Fill the glass with crushed ice and add the Cachaça.
Joseph Purcell, from Palantir in Madison, Wisconsin has another interesting metaphor: Technical pollution
Slides here: https://josephdpurcell.github.io/Lorax/dist/2015-madison-php/index.html#/
and a video of his presentation: