• marlowe221@lemmy.world
    link
    fedilink
    English
    arrow-up
    17
    ·
    4 days ago

    I might be in the minority, but I get more excited about the idea of maintaining/working on some creaky old legacy code base than I do about the idea of starting a new project from scratch.

    • NigelFrobisher@aussie.zone
      link
      fedilink
      arrow-up
      2
      ·
      3 days ago

      I enjoy this too, but it’s kind of rough when you’ve inverted control, teased apart unnecessary coupling, updated dependencies and backed everything with unit and other tests, but then your colleagues are too scared to code review it.

    • ambitiousslab@lemmy.ml
      link
      fedilink
      English
      arrow-up
      3
      ·
      4 days ago

      Yes, me too! But, only if I have the autonomy to improve things where I can. Otherwise, I just find it demotivating

    • masterspace@lemmy.ca
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      4 days ago

      I find that working on production code with well defined use cases and requirements to be the most satisfying, and working on new proof of concept / demos / marketing tools to be the least satisfying.

      So on balance, more of the legacy projects I’ve worked on have fit those criteria than the new builds, but the couple of new builds that had well defined use cases, and no legacy code to deal with were the absolute best.