• bluGill@fedia.io
    link
    fedilink
    arrow-up
    0
    ·
    28 days ago

    I’ve been writting a lot of code with ai - for every half hour the ai needs to write the code I need a full week to revise it into good code. If you don’t do that hard work the ai is going to overwhelm the reviewers with garbage

      • bluGill@fedia.io
        link
        fedilink
        arrow-up
        0
        ·
        28 days ago

        I’m writing code because it is often faster than explaining to the ai how to do it. I’m spending this month seeing what ai can do - it ranges from saving me a lot of tedious effort to making a large mess to clean up

        • Joe@discuss.tchncs.de
          link
          fedilink
          English
          arrow-up
          0
          arrow-down
          1
          ·
          28 days ago

          You will need more than a month to figure out what its good for and what not, and to learn how to effectively utilize it as a tool.

          If can properly state a problem, outline the approach I want, and can break it down into testable stages, it can be an accelerator. If not, it’s often slop.

          The most valuable time is up front design and planning, and learning how to express it. Next up is the ability to quickly make judgement calls, and to backtrack without getting bogged down.