A two-minute interactive audit to score whether technical debt is dragging your engineering team. Five signals that separate people problems from code problems.

A client’s team spent a full week adding a CSV export to their admin panel. Two engineers, clear requirements, maybe a day of actual work. The rest of the time went to understanding existing code well enough to change it safely. That’s what I call codebase drag: when the codebase makes every task take longer than it should. It doesn’t show up in any dashboard or sprint report.

  • beeng@discuss.tchncs.de
    1·
    7 hours ago

    So did we make it to “codebase drag” yet?

    Something that isn’t debt but is a headwind to making changes.

    • Ethan@programming.devEnglish
      1·
      5 hours ago

      If we’re talking about the Linux kernel or Netflix’s video delivery infrastructure, maybe. But the majority of developers are not working on those. And I’m still going to call it “unavoidable technical debt” because for all intents and purposes that’s what it is.