Technical debt is, in a way, just like financial debt. We'll take a look at how it influences, even stifles, every aspect of our work, from the decision which features we develop, to extra planning efforts, to the actual development of new features taking extra time – and we'll see how to get rid of technical debt in the long run.
These are the slides for my talk about Technical Debt at PHPBenelux 2016. This slidedeck is licensed under CC-BY-SA 3.0.
Image credits:
"Paperwork": Camilo Rueda López (flickr) - CC-BY-SA 2.0
"Budget": TaxCredits.net (flickr) - CC-BY 2.0
"Snowball": ff137 (flickr) - CC-BY 2.0
"Cleaning Supplies": Chiot's Run (flickr) - CC-BY-NC 2.0
"Scout Jamboree Memorial Sculpture": Gnangarra (Wikipedia) - CC-BY 2.5
"Be Bold": Wapcaplet, Oile11 (Wikipedia) - CC-BY-SA 3.0
"Scattered puzzle pieces": Horia Varlan (flickr) - CC-BY 2.0
"Assembly knolling": Brian Boucheron (flickr) - CC-BY 2.0
"Value": GotCredit.com (flickr) - CC-BY 2.0
"Good Debt": GotCredit.com (flickr) - CC-BY 2.0
"Rainbow of Credit": frankieleon (flickr) - CC-BY 2.0
tobiasgies
umizaru
xblood
shoheihosaka
77web
mukky620
totto2727
danilop
tmokmss
totokit4
qualiarts
mraible
masuda220
edds
pauljervisheath
sonatard
tmm1
searls
jcasabona
iamctodd
shpigford
smashingmag
maltzj
jennybc
kneath