Managing Technical Debt

Adam Culp (28.Jul.2018 at 10:00, 45 min)
Talk at PHPDetroit Conference 2018 (English - US)

Rating: 5 of 5

Every change to a codebase increases technical debt leaving it less stable, bug-prone, and closer to technical bankruptcy requiring a rewrite. Let's explore how to measure technical debt to gain a score and highlight the current condition of a PHP application. We will then introduce simple steps for improving code quality, deliver new features faster, and lower project stress.

Who are you?

Claim talk

Talk claims have been moved to the new Joind.in site.

Please login to the new site to claim your talk

 
Comments closed.

Comments

Rating: 4 of 5

28.Jul.2018 at 13:21 by Philip Sharp (62 comments) via Web2 LIVE

A lot of information crammed into this talk (and on the slides). Would be interesting to also consider what isn't technical debt, since the term is often used so loosely.

Rating: 5 of 5

28.Jul.2018 at 14:26 by TJ McKenzie (9 comments) via Web2 LIVE

Great talk. Adam gives a lot of good advice about refactoring over time, to tackle technical debt.

Rating: 5 of 5

28.Jul.2018 at 15:10 by Steve Grunwell (135 comments) via Web2 LIVE

Great talk, though the content bordered more on code quality and preventing technical debt in the first place rather than digging out from under existing debt. Prices on the slides — especially when some are in Euros and others in USD — were also somewhat distracting; it might make sense to leave off specific pricing in the future.

Rating: 5 of 5

28.Jul.2018 at 21:22 by Jake Moote (5 comments) via Web2 LIVE

Good talk on why technical debt is bad and some tips on how to avoid it. Adam also seemed very comfortable and experienced as a speaker and was very engaging. I agree with Steve that it may have been nice to hear a bit more about dealing with already accrued technical debt.

© Joind.in 2018