Damus
SatsAndSports profile picture
SatsAndSports
@SatsAndSports
After big code changes, ask your agent if there were any surprises while it was working. I always find it interesting; sometimes it raises important details that it otherwise wouldn't have told me about

Ask it what changed and what didn't. If you think that a particular task is a conventional refactor of a particular module and it shouldn't affect any tests or any other modules, it's good to verify this afterwards




6
SatsAndSports · 7w
https://image.nostr.build/2346477bf82a57112341b1d89552d2c8b4f653afb08b94119b42e15a7471cfac.png
Billy Bapparoo · 7w
I use something similar : "Assess how you did, with what you know now, if you were to repeat this what would you change or do differently." Sometimes I think, why didn't you do that in the firstplace ๐Ÿ˜. Also getting it to save those bits of feedback that make sense. I'll try your method next time...