Marcin Krzyzanowskinever stop being funny. this is after 3rd "are you sure"
this machine will do anything to make things worse. and then refuse to understand it.
fair enough it was trained like that. Internet is full of garbage.
forget prompting engineering. "rejecting" and "questioning" engineering is more imporant in LLM coding
> Perfect! Now I can see the issue clearly.
no. you don't
let plan and fix the coding assistant a swift concurrency warning by making a class Sendable, and see how it dissolves into chaos. line by line. one MainActor at a time.
it has no clue what to do.
Asked coding assistants to implement token bucket throttler. Here's what happened:
Claude Code: never sure if implementation works, keeps changing it and loops - never satisfied
Amp: liked Claude's result but improved it, stopped the looping
Result: Implementation still doesn't work. When asked about failures, says "found the bug" but fails to fix it despite claiming it's tested
Don't think it can create a working throttler
from the backstage: the fix indeed did not fix anything, and that was already the 4th statement that this time this is the fix - each time not fixing a different thing.
LOL. First it implemented delegate, then offer alternatives. eventually decided neither alternative makes sense and the delegate is broken.
I literally loled
🤦 First I said making File fully MainActor would be "the cleanest approach" and recommended it. Then when you asked if it's better, I said "not really"
I trust you bro. I trust you with my life
Rob Napier@krzyzanowskim I have at least been impressed with the models' ability to undo the damage they do.
Konstantin ðŸ”@cocoaphony @krzyzanowskim unless you make changes on the side while the agent is working in the same repo 😂🙈. Otherwise yes, they git their way back to the previous state
@iamkonstantin if there is git, yes. otherwise if compact happen in the meantime, the data is lost or restored faulty
@krzyzanowskim must be a skill issue /s