3 ms·
I agree that probably not everything should be stored - it’s too noisy. But the reason the session is so interesting is precisely the later part of the conversa
by solarkraft 8mo ago
I agree that probably not everything should be stored - it’s too noisy. But the reason the session is so interesting is precisely the later part of the conversation - all the corrections in the details, where the actual, more precise requirements crystallize.
- slashdave 8mo agoThen just summarize the final requirements
- solarkraft 8mo agoThat’s what I do! I think it works well and helps future agents a lot in understanding why the codebase is the way it is. I do have to oversee the commit messages, but it does avoid a lot of noise and maybe it’s a normal part of HITL development.
- lsaferite 8mo agoIf it's non-trivial work, have the Agent distill it down to an ADR.
- insin 8mo agoAKA the code. You're all talking about the code.
- medstrom 8mo agoThe prompt is the code :) The code is like a compiled binary. How long until we put the prompts in `src/` and the code in `bin/`, I wonder...
- kubanczyk 8mo agoI call out false dilemma. OP probably defines "code" as one of the languages precise enough to be suited for steering Turing machines. Thus, "code" is not the opposite of "prompt". They are apples and oranges. Lawyers can code in English, but it is not to layperson's advantage, is it? And for example, if you prompt for something to frobnicate biweekly, there is no intelligence today, and there will never be, to extract from it whether you want the Turing machine to act twice a week or one per two weeks. It's a deficiency of language, not of intelligence.
- whywhywhywhy 8mo agoPeople are trying to retain value as their value is being evaporated.
- solarkraft 8mo agoNot at all, unless it contains very thorough reasoning comments (which arguably it should). The code is only an artifact, a lot of which is incidental and flexible. The prompts contain the actual constraints.