• marlowe221@lemmy.world
    link
    fedilink
    English
    arrow-up
    165
    arrow-down
    2
    ·
    2 days ago

    Can someone, anyone, tell me where it is that you work where input speed is the bottleneck in software development?

    Because I have genuinely never worked at any company where the main thing holding up development was that developers weren’t typing fast enough.

    • Zarobi@aussie.zone
      link
      fedilink
      English
      arrow-up
      20
      ·
      edit-2
      22 hours ago

      Once I was basically the only programmer on a huge project (“superstar”). One day I injured my hands from working too hard, and had to use assistive technologies.

      The entire project ground to a halt, and management was on my ass all day every day about productivity. I even got a write-up and my bonus cancelled because I went from 3x output to 1.2x output (compared to my coworkers). Obviously I didn’t stay long after that…

      So yeah, if you’re in that extremely niche type of situation, it probably matters. Creating an entire project by yourself kind of jobs. Actually, that tool looks extremely good for people who cannot use a mouse and keyboard for any reason. I would have used it. I didn’t like speaking to my computer to write out code in an open plan office.

      Edit: this was way before A.I., so I meant literally those voice commands. Change tab to x. Type: while, space, open parenthesis, true, close parenthesis, space, open bracket… my coworkers got annoyed.

    • PattyMcB@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      21 hours ago

      Companies (garbage ones) where they measure “productivity” by AI token use, number of code commits, or lines of code written.

    • definitemaybe@lemmy.ca
      link
      fedilink
      arrow-up
      74
      arrow-down
      1
      ·
      edit-2
      1 day ago

      When you’re vibe coding, you need to narrate long prompts, including things like “And remember not to hallucinate or make any errors.” All that is a lot faster to say than type.

      Clearly, you’re not vibe coding, and your job will be (checks notes) automated away by someone with a #grindset.

      /s, in case that wasn’t obvious.

      • Goodeye8@piefed.social
        link
        fedilink
        English
        arrow-up
        17
        ·
        1 day ago

        Actually the tooling is such that you have that written in some kind of a rules file that will then more or less append the rules to the prompt so you wouldn’t have to repeat it over and over.

        At least I think that’s how it works, I was only half listening to the mandatory AI training.

      • DisasterTransport@startrek.website
        link
        fedilink
        arrow-up
        23
        arrow-down
        1
        ·
        edit-2
        1 day ago

        If youre not using a custom instruction that brute forces different ways to try to get the other model not to fuck uo youre doing it wrong. If that doesn’t work, add another llm into the pipe

        Edit what is a token and why is my boss sending me angry emails

        • Croquette@sh.itjust.works
          link
          fedilink
          arrow-up
          15
          ·
          21 hours ago

          I was talking to an acquaintance and she was taking AI course.

          She was taught to “validate” LLM infos by asking the same question in a different model.

          This is an actual university course.

          I was baffled. There is no guarantee that both models aren’t wrong. But speaking to people that use LLMs, this is a common strategy.

        • TheMadBeagle@lemmy.ml
          link
          fedilink
          arrow-up
          6
          ·
          1 day ago

          God how i wish anyone I worked with understood throwing bodies at every problem doesn’t mean it gets fixed faster. On the the other end of problems, they don’t understand a developer can’t just start developing on immediately on complex application.

          God being in project orient work is a pain.