News for hackers. Stuff that matters.
Re:Why LLM-Powered Programming Is More Mech Suit Than Artifi... by lherron on Monday April 21, 2025 @12:44PM (#43753905)
I agree for method-level changes, but the more you’re willing to cede control for larger changes, even in a familiar language, the more an LLM accelerates you.

For me, I give Gemini the full context of my repo, tell it the sweeping changes I want to make, and let it do the zero to one planning step. Then I modify (mostly prune) the output and let Cursor get to work.

Re:Why LLM-Powered Programming Is More Mech Suit Than Artifi... by AdieuToLogic on Monday April 21, 2025 @07:55PM (#43757741)
> I agree for method-level changes, but the more you’re willing to cede control for larger changes, even in a familiar language, the more an LLM accelerates you.

Another way to phrase this is:

  I agree for method-level changes, but the more you’re 
  willing to cede *understanding* for larger changes, even in 
  a familiar language, the more an LLM accelerates you *to an 
  opaque change set*.
Without understanding, the probability of a code generation tool introducing significant defects approaches 1.
Re:Why LLM-Powered Programming Is More Mech Suit Than Artifi... by tsimionescu on Tuesday April 22, 2025 @04:06AM (#43760038)
> For me, I give Gemini the full context of my repo, tell it the sweeping changes I want to make

If the full context of your repo (which I assume means more or less the entire git history of it, since that is what you usually need for sweeping changes) fits into Gemini's context window, you're working on a very small repo, and so your problems are easy to solve, and LLMs are ok at solving small easy problems. Wait till you get to more than some few thousand lines of code, and more than two years of Git history, and then see if this strategy still works well for you.