When you call the humans who keep production safe “the bottleneck” you’re painting a very specific picture. The reviewer as the obstacle. The gate as friction. Something to route around. Cue in the Balrog scene from Lord of the Rings. That picture determines what you build. The tools to remove reviewers look different from tools to support them.

  • FishFace@piefed.social
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    6
    ·
    6 days ago

    Writing lines of code was the bottleneck before. Vetting them is the bottleneck now, if LLMs are involved.

    • tyler@programming.dev
      link
      fedilink
      arrow-up
      9
      ·
      6 days ago

      writing lines has never been the bottleneck, that’s only something a junior would say. The bottleneck is always requirements: changing, understanding them, making sure you don’t miss test cases before writing any code.

      • FishFace@piefed.social
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        6 days ago

        test dogmatist detected

        No, the bottleneck is not always requirements. Understanding requirements is a prerequisite to writing correct code, but it takes a fraction of the time.

        Obviously different domains have different complexities of requirements and code which changes the ratio

        • ulterno@programming.dev
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 days ago

          Yeah, e.g. writing UI code takes a lot of time, while it tends to be pretty simple overall and that’s why we have so many UI toolkits, to reduce the amount of writing required for UI.

          • FishFace@piefed.social
            link
            fedilink
            English
            arrow-up
            4
            ·
            6 days ago

            Instead of spending 4 weeks writing requirements and 1 week implementing them, have you tried spending a day guessing at requirements, half a week writing a prototype, and then asking the customer if it works for them?

            Have you ever worked on a tools team where your customers are internal and your developers are also customers and so know the requirements inside-out?

            • ulterno@programming.dev
              link
              fedilink
              English
              arrow-up
              1
              ·
              5 days ago

              Hehe! I have.
              And what took the longest was for me to get used to the dual versioning of QML modules and fixing the UI code that was partially using stuff from both versions.

              Business logic was pretty small for me but that was because other engineers had already written most of it in Maths.

    • TrippinMallard@lemmy.ml
      link
      fedilink
      arrow-up
      4
      ·
      6 days ago

      The bottleneck was human ego and people not actually having enough experience for designing complex systems. Or people without enough experience setting up people systems that interfere with those who can actually design the systems.