Technical Debt - #phpbnl16

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

Transcript

1. TECHNICAL DEBT Why it's crippling you and what to do
2. Technical Debt is aptly named
3. Excursion:
5. Small things can cause a snowball effect
6. Result:
7. New code must be clean „Any fool can write code that a computer can understand. Good programmers write code that humans can understand.“ – Martin Fowler
8. Old code must be improved "Always leave the campground cleaner than you found it." – Boy Scout rule
10. Break apart large functions
11. Separate concerns
12. Value Objects
13. More improvements • Object Calisthenics • Fowler: Refactoring
14. Does it exist?
15. „Ehh, I'll just hack this“
17. Thanks! Tobias Gies Email: tobias@tobiasgies.de Twitter: @tobiasgies Rate this talk: https://joind.in/16942