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

    Damn right. I care about getting features in the hands of my users. If code quality helps with that, if type script helps with that, I’m all in favor.

    But the moment I care about code quality for its own sake you need to sack my ass like yesterday.

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

      What an utterly blind, self-centered view. Write good, readable code so you can actually maintain it and so your coworkers don’t want to kill you.

      • aport@programming.dev
        link
        fedilink
        arrow-up
        5
        ·
        1 year ago

        I think vzq’s point is that you can write good, readable code that doesn’t do what the user wants. Same with other metrics that are ripe for navel-gazing like code coverage.

        It’s bordering on a false dichotomy… but I also believe that dynamic, untyped languages have proven exceptionally useful for rapid prototyping and iteration.

        • vzq@lemmy.blahaj.zone
          link
          fedilink
          arrow-up
          9
          ·
          edit-2
          1 year ago

          I must admit that I write that deliberately to annoy the “code quality is everything” brigade.

          I have no issues prioritizing maintainability where needed, but in my experience people that dogmatically prioritize code quality are not honest with themselves. They almost never chase code quality in general. They are always looking to enforce some burdensome standard or specific tool or archaic process or fiddly CICD script, and if you push back they go cry in a corner about the abstract virtue of “code quality”.

          Just be straight with me. You enjoy using type script. Tell me how it adds value to the product and the customer.

          Stop trying to shame me into it. I can’t be shamed. I have no shame. I’m a professional software engineer.

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

            You’re setting up a theoretically boogie man that no one said exists and then setup the extreme opposite point of view. You’re annoying the people that are actually sane. You’re being dogmatic in your one views and too extreme.

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

                  It’s a business decision. Why would for example an app that’s only needed for a 24 hour event need to be maintainable?

                  Sometimes it’s ok to take the money and run. Feel free to make your case, but it’s not a developer’s call to make.

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

                    That sounds like bad business. No application is 100% unique in everything. Code reuse saves time. If you are unable to bring anything from one app to another, you’re doing it wrong.

                    Let me guess though, I was right. You’re a manager not a developer.

        • pitbuster@lemmy.ml
          link
          fedilink
          arrow-up
          6
          ·
          1 year ago

          but I also believe that dynamic, untyped languages have proven exceptionally useful for rapid prototyping and iteration.

          Except that prototypes never end up as just prototypes, they die or become the real app with lots of masking tape.

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

        What an utterly blind, self-centered view.

        This is a really surprising retort.

        In the end, the only thing that has value is what ends up in the user’s hands. The rest is only a means to an end, in the very best case.

        This is not a controversial take in professional software development.

        What is self centered and self absorbed is putting misguided notions of “craftsmanship” and maintainability over business needs.

        • eltimablo@kbin.social
          link
          fedilink
          arrow-up
          18
          ·
          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@lemmy.blahaj.zone
            link
            fedilink
            arrow-up
            3
            ·
            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
              9
              ·
              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.

      • Amju Wolf@pawb.social
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        But you can do that in vanilla JS, too.

        Even better, don’t use JS at all if you don’t have to.

        You can write shitty code in TS too.

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

      maintainability is arguably not a value-added for the end user. But still absolutely important. Robustness of code is arguably not visible to an end-user, until it fails. And that’s very important. Features are great, but quality is still important and is basically the mortar between the bricks that are features. Only caring about features leads to poorly written applications.

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

        Less chance of security vulnerabilities, breaches, less bugs fixed more permanently, faster features, etc

        Those things all sound like value adds for the end user…