The really interesting part is IMO this one:

  • Blackmist@feddit.uk
    link
    fedilink
    English
    arrow-up
    22
    ·
    1 month ago

    Technical debt is a real doozy. There’s no value for the higher ups in fixing it, so nobody does.

    New features just take longer and longer to add, under a teetering pile of your own shit.

    I think part of the problem is the ideal underlying structure for your project doesn’t really reveal itself until several years in, and by then it’s a nice to have for some other time that never arrives.

    • steeznson@lemmy.world
      link
      fedilink
      arrow-up
      12
      ·
      1 month ago

      Tech debt is like a hole in your roof that many teams don’t start trying to fix until water is flooding in. Companies missing the business value in addressing tech debt leads to perverse incentives for developers where they are encouraged to cram new features into the product and then leave for another job in 2-3 years before the consequences come knocking.

    • FizzyOrange@programming.dev
      link
      fedilink
      arrow-up
      4
      ·
      1 month ago

      There’s no value for the higher ups in fixing it

      Well there is, it’s just long term value that they don’t even understand.

      Really you should just make fixing technical debt part of your regular job. Don’t ask for permission, just do it. (Except for really big things obviously.)