1144
Now listen here you little shit (thelemmy.club)
submitted 5 months ago* (last edited 5 months ago) by to c/programmer_humor@programming.dev
105 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 0 points 5 months ago (3 children)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 14 points 5 months 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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 5 points 5 months 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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 5 months 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.

  • permalink
  • fedilink
  • source
  • parent