• jonathan7luke@lemmy.zip
    6 months

    Sharing this from the article to hopefully save the post a few downvotes:

    Coding was never the bottleneck. Not recently. Not in the last decade. Arguably not since we stopped feeding punchcards into machines.

    Coding was never the bottleneck astronaut with gun meme

    • resipsaloquitur@lemmy.world
      6 months

      Kind of on the author for giving the article a clickbaity title.

      Today there’s lots of interest in “specification driven development” with GenAI as if it’s the hot new thing.

      Agree with the author — “specification driven development” is like saying cold ice cream is the hot new thing.

    • Gonzako@lemmy.world
      6 months

      I feel this so much. I started doing a rewrite of a plugin wanting to understand how it does its work and the real bottleneck is not knowing what’s being done, not how to write it down

  • Technus@lemmy.zip
    6 months

    I’ve long maintained that actually writing code is only a small part of the job. Understanding the code that exists and knowing what code to write is 90% of it.

    I don’t personally feel that gen AI has a place in my work, because I think about the code as I’m writing it. By the time I have a complete enough understanding of what I want the code to do in order to write it into a prompt, the work is already mostly done, and banging out the code that remains and seeing it come to life is just pure catharsis.

    The idea of having to hand-hold an LLM through figuring out the solution itself just doesn’t sound fun to me. If I had to do that, I’d rather be teaching an actual human to do it.

  • dontsayaword@piefed.socialEnglish
    6 months

    Was writing code the bottleneck before? Or was it planning, alignment, learning, iteration, testing, etc?

    • limer@lemmy.ml
      6 months

      I can hand write a lot very fast, but it only had value when I do the above.