pull down to refresh

43 sats \ 4 replies \ @optimism 2 Sep \ parent \ on: Stacker Saloon

Maybe we need to bring back the ralphwiggin skill for reviews so that we get all the findings at once instead of dripping them in, because I think the most annoying part, especially with recent Claude "improvements", is that it always leaves things out. I rarely get a list with more than 12-15 findings, then after addressing these, another 12-15 findings.

write
compose
173 sats \ 3 replies \ @SimpleStacker 2 Sep

Not sure how it is for code review, but for research review you sometimes get this cycle

  1. This finding is interesting, you are selling it too short, you should emphasize it more!

--> go back and emphasize that result

  1. You are overselling this result. Your interpretation is not justified by the evidence. Tone down your claims!
reply
126 sats \ 1 reply \ @Undisciplined 2 Sep

Those typically occur in the same round of reviews by different reviewers.

I have yet to have the same reviewer give me that feedback in successive rounds.

reply
48 sats \ 0 replies \ @optimism 2 Sep

I've had it on a bug a week and a half ago. The first review told me "this is incomplete so add xyz", the second (after implementing it) said "remove xyz because it goes against spec".

reply
1 sat \ 0 replies \ @optimism 2 Sep

oh. Yeah that's different for me. I expressly ask for evidence, and often even don't ask for solutions. There's still a similar symptom, but just like I don't argue with bots, I really do not give 2 shits about the opinion of a bot. Execute the task, and hup hup.

reply