• eltimablo@kbin.social
    link
    fedilink
    arrow-up
    20
    ·
    edit-2
    1 year ago

    If you can’t see that writing readable code is part of the means to that end, I don’t know what to tell you. If nobody can maintain the codebase because it’s a mess of spaghetti logic and 20-deep dependency trees (I’m looking at you, every JavaScript project I’ve ever seen), the end product is going to suffer while also making every single engineer working on it want to leave.

    This is not a controversial take in professional software development.

    Funny, it sure seems like “maintainability should not be a priority” is a pretty controversial take to me.

    • vzq
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      2 months ago

      deleted by creator

      • eltimablo@kbin.social
        link
        fedilink
        arrow-up
        11
        ·
        1 year ago

        In my world we prioritize one. And that not the one.

        Then I’m really glad I don’t live in that world.

      • pjhenry1216@kbin.social
        link
        fedilink
        arrow-up
        7
        ·
        1 year ago

        In my world we prioritize one.

        Weird. In most cases priorities change as the situation demands. The application doesn’t matter when it comes to maintainability. Tech debt will take down any application if you keep ignoring maintainability at the expense of just delivering more and more. You sound more like a manager than a developer.

        • RandoCalrandian@kbin.social
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          Even their excuses if a “24h only event app” don’t hold water

          Even in that case, a business would be wanting to make many of those apps, and this commenter is arguing making a new one from scratch every time over massively simplifying things with quality reusable code.

          Even their own example shows how terrible it is an idea to deprioritize code quality/readability.