• vzq@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    1 year ago

    You are making a lot of assumptions. You don’t know what my product is, how it is developed, what it’s used for, what its lifecycle is. Whether improving maintainability or code quality would be a net benefit, and whether using type script would be a possible solution.

    You also didn’t bother to find out.

    You just charge at me guns blazing, trying to string me up for heresy.

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

    How many things can you prioritize?

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

    • eltimablo@kbin.social
      link
      fedilink
      arrow-up
      11
      arrow-down
      1
      ·
      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.