Thread

1. lm2s · 1790322574 · focus · HN ↗

   I think your engineering process is fundamentally broken if you are generating PRs with 230 files changed so regularly that you need to bolt on more AI. You’re solving the wrong problem.

   1. stuaxo · 1790324854 · focus · HN ↗

      That really stood out.

      Code is there to be read and understood by the human developers who come later.

      The git history is a similar record, that's why the commits that make it to main (the squashed PRs) should cover one(ish) thing each and be self contained.

      Something covering 230 files should be a mechanical change like running a linter or the AI is moving an API from one signature to another.

      If an LLM generated a 230 file change they are also capable of going back and breaking it up.

      One thing they are bad at is comments that are succinct since they almost only ever add words.

      1. moffkalast · 1790327135 · focus · HN ↗

         > human developers who come later

         Tbf, once the codebase is slopped enough that becomes impossible and only LLM can come later.

         1. latentsea · 1790328151 · focus · HN ↗

            Yeah, we should push back on this. We don't have to accept this outcome as if it's inevitable.

            1. munksbeer · 1790334974 · focus · HN ↗

               It is inevitable. We (coders) already did it to other engineering disciplines where machines do most of the work, no human could possibly review or understand the actual details, and only verification ensures it is correct.

               Why do you think coding is immune to this?

               1. discreteevent · 1790337179 · focus · HN ↗

                  > no human could possibly review or understand the actual details,

                  What are you talking about? - The developers understood it. Did my car manufacturer do something to my discipline because I don't understand my car?

                  1. munksbeer · 1790345290 · focus · HN ↗

                     Look up Constraint-Driven Design or Declarative Engineering
               2. latentsea · 1790345595 · focus · HN ↗

                  Call me old fashioned, but things were working just fine.

Unofficial Hacker News client; not affiliated with Y Combinator.