• marlowe221@lemmy.world
    link
    fedilink
    English
    arrow-up
    169
    arrow-down
    1
    ·
    3 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.

    • JackbyDev@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      13 hours ago

      Assuming this is a real post and not satire, my best guess is that they don’t think it’s a bottleneck, but still believe a way to talk to the computer without disturbing others in the office is useful. Like if Tide detergent said it would save your marriage – they don’t think it really will, but the ad is humourous and likely to gain attention because of it.

    • Zarobi@aussie.zone
      link
      fedilink
      English
      arrow-up
      22
      ·
      2 days 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.

    • definitemaybe@lemmy.ca
      link
      fedilink
      arrow-up
      78
      arrow-down
      1
      ·
      3 days 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
        21
        ·
        2 days 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.

        • ozymandias117@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 day ago

          Wondering if those AI trainers know every character you put in that file is another token they’re paying for

    • PattyMcB@lemmy.world
      link
      fedilink
      arrow-up
      8
      ·
      2 days ago

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

        • TheMadBeagle@lemmy.ml
          link
          fedilink
          arrow-up
          7
          ·
          3 days 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.