• OsrsNeedsF2P@lemmy.ml
    link
    fedilink
    arrow-up
    13
    ·
    6 days ago

    At my company we allocate 20% of our time on “Better engineering”, and it counts as impact when you’re up for bonuses/raises so people actually have a reason to push to do it

    • eldavi@lemmy.ml
      link
      fedilink
      English
      arrow-up
      8
      ·
      6 days ago

      i saw something like this once and their source was the neatest and most professional i’ve ever seen and it’s convinced me that this is the only way refactoring ever happens.

  • Ephera@lemmy.ml
    link
    fedilink
    English
    arrow-up
    11
    ·
    6 days ago

    Worst part is when the un-refactored code continues to confuse other devs, meaning it keeps causing additional work, but you still don’t get time to actually fix it.

    • CarrotsHaveEars@lemmy.ml
      link
      fedilink
      arrow-up
      4
      ·
      6 days ago

      Commit1: actual change
      Commit2: this code is so misleading and I have to refactor it refactors
      Me: painfully rejects PR the story said nothing about refactoring…

      • collapse_already@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 days ago

        The mistake is admitting that you’re refactoring. I just implemented the feature/ fixed the bug. Why did I change so much? The issue was a little underscoped.

        The fun thing is to try to force your fellow devs to refactor piecemeal through comments on their pull requests.

  • jade52@lemmy.ca
    link
    fedilink
    arrow-up
    2
    ·
    5 days ago

    Don’t forget about the fabled but often discussed “tech debt sprint”.