3 ms·
Yea but then you need need to commit each iteration of each file right away, even if its not working. Its fine if you just rebase at the end manually, but not
by hoppp 1y ago
Yea but then you need need to commit each iteration of each file right away, even if its not working.
Its fine if you just rebase at the end manually, but not good if you don't, your history will be cluttered and as hard to read as the codebase.
Eventually most people who use coding tools will have low knowledge of what is being generated and then they probably never rebase either...
- samtheprogram 1y agoYup, just rebase. I just commit with a “wip!”-prefaced message whenever the LLM pauses and says it’s finished, including new files. You can squash and cleanup later, or revert back to a state before it screwed up. Also doubles as a way to cohesively look at the changes it made without all the natural language and recursive error/type fixing it does while working. I don’t understand why people are making it so complicated. You’re saving a minute per iteration with the LLM, tops, at risk of losing control or introducing hard to find issues. It is the definition of diminishing returns.