Damus
jb55 profile picture
jb55
@jb55
one great tip i learned from the Peter Steinberger interview: https://www.youtube.com/watch?v=YFjfBk8HI5o

"ask the agent how would it have done it differently"

since it tends to rush through the first time, letting it think about how to do it better after implementing is suprisingly productive. implement + refactor is a great pattern.
111โค๏ธ15โค๏ธ4๐Ÿค™2โค1๐Ÿ”ฅ1๐Ÿ˜‚1
Patoo · 13h
dis is real. the retrospective prompt unlocks a different mode โ€” agent stops optimizing for speed and starts reasoning about quality. also works in reverse: "what would you check before starting?" forces it to surface assumptions it would otherwise skip. two-pass pattern hit different. ๐Ÿ”ฅ
Noelyne · 13h
Good suggestion, thanks
TKay · 13h
nostr:npub1r0d8u8mnj6769500nypnm28a9hpk9qg8jr0ehe30tygr3wuhcnvs4rfsft we were just talking about this.
Diyana · 13h
Cool tip. I always ask my AI, how do you rate it? (your response, etc.) So it then goes ahead and breaks it down and evaluates potential improvements.
ABH3PO · 13h
Whenever i pose a "problem" to the llm i add a "wdyt?" At the end, that way it researches gives an opinion, makes a plan instead of jumping to code, huge difference in quality if it plans first and if you can give an input in its plan itself.
GJM · 13h
I have just started the process of telling ChatGPT what Codex is doing/just did. Both apps open at the same time. Very, very interesting.
florian · 12h
Yes. and asking for refactoring after a task is done.
Rik ๐Ÿ”ฅ ๐Ÿ” ๐Ÿƒ ๐ŸŒŠ · 9h
Red, green, refactor
Bitcoin Babies ๐Ÿผ · 6h
Good tip