The next Developer SIG meeting is now up on eventbrite, so feel free
to sign up if you plan to come!

Addressing Technical Debt

Maybe it was a shortcut taken to get a feature out the door faster…
or a poor architecture decision that is too expensive to change now…
or maybe a developer checked in code that looked perfectly fine to
them, but it really needed a few more eyes…

However it got there, today we have a problem.  Technical Debt.
Whenever we have to understand or change this code, it eats away
countless hours and can make quality a near impossible endeavor.  If
you are unfortunate enough to have to deal with this code every day,
the pain might be constant.

In this discussion, we will explore some of the group’s ideas and
discoveries on addressing technical debt. (in priority order)

  • How do you stop accumulating technical debt?
  • How can you quantify the impact of technical debt and prioritize what should be fixed first?
  • How can you identify and measure technical debt in code?
  • How do you get buy in or justify spending time working on technical debt?