Re:The Coming Knowledge-Work Supply-Chain Crisis
by samjewell on Sunday April 27, 2025 @05:19PM
(#43815227)
> In fact, you should commit your LLM dialogs along with your code.
Wholeheartedly agree with this.
I think code review will evolve from "Review this code" to "Review this prompt that was used to generate some code"
Re:The Coming Knowledge-Work Supply-Chain Crisis
by roguecoder on Monday April 28, 2025 @01:58PM
(#43824154)
All LLM output is non-deterministically wrong. Without a human in the loop who understands the code, you are stochastically releasing broken, insecure, unmaintainable software.
Any software engineer who puts a stamp of approval on software they have not read and understood is committing professional malpractice.
Re:The Coming Knowledge-Work Supply-Chain Crisis
by anonzzzies on Monday April 28, 2025 @12:26AM
(#43817551)
> In fact, you should commit your LLM dialogs along with your code.
Absolutely, for different reasons including later reviews / visits to the code + prompts.
Re:The Coming Knowledge-Work Supply-Chain Crisis
by ithkuil on Monday April 28, 2025 @03:44AM
(#43818673)
I wonder if some sort of summarization / gist of the course correction / teaching would work.
For example Cursor has checked-in rules files and there is a way to have the model update the rules themselves based on the conversation
Re:The Coming Knowledge-Work Supply-Chain Crisis
by roguecoder on Monday April 28, 2025 @01:56PM
(#43824141)
We've tried Literate Programming before, and it wasn't helpful.
Mostly because we almost never read code to understand the intention behind the code: we read it to figure out why the fuck it isn't working, and the intentions don't help us answer that.
However, this creates a significant return on investment for opensourcing your LLM projects. In fact, you should commit your LLM dialogs along with your code. The LLM won't learn immediately, but it will learn in a few months when the next refresh comes out.