• Tja@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    16 hours ago

    Well, if rewriting is maintaining, everybody can write maintenable code.

    Did it become a mess? Rewrite time!

    For me the art is writing it so you don’t need to rewrite and you don’t need a janky temporary permanent workaround if requirements change. Clean interfaces, SOLID, plug-ins, etc. Can’t do it myself, but the legendary 10x devs usually do.

    • red_tomato@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      14 hours ago

      The most maintainable code is built to be replaced with minimal impact.

      How much of the program will must be replaced if you remove one module? If you need to replace the entire program, then your program is not maintainable. Too much is heavily dependent on this module.

    • 0ops@piefed.zip
      link
      fedilink
      English
      arrow-up
      0
      ·
      14 hours ago

      I don’t believe in code that never needs a rewrite, but scalable code should be compartmentalized and future-proofed to the point that the next rewrite can be pushed as far into the future as possible. Me personally, I tend to discover what these best practices are during those rewrites.

    • brygphilomena@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      0
      ·
      15 hours ago

      All code is maintainable with enough time and money.

      But yes, well structured code where those rewrites are minimal is the goal.

      There probably is a threshold where the amount you have to rewrite becomes too high. But with each rewrite, hopefully the next time you have a section you need to redo its smaller that before. Eventually going from rewriting a couple thousands of lines to just a hundred or so on the 5th iteration.