Raw LLM Responses

Yep, found an issue with something I was testing yesterday where if I opened something on a page one way I got the new thing I added, but if I opened it another way it didn't show up unless I clicked something else on the page after it loaded. Fired up Claude, told it the problem ("If I get to it this way I see the thing, but if I get to it this other way I don't see it unless I click on this other entry on the page first."), let it cook for a bit, and it found the issue, explained why it happened, and proposed a fix. Wasn't entirely satisfied with its suggestion so I asked why it settled on that, and it came up with a better one that I told it to implement. The plugin I'm using ran a quick review of the changes and said it all looks good but notes this increases the number of calls to an API and caching the value after the first call would be a good next step, so I tell it to do that too. Project builds, so I run it locally to verify I get the result I want, put it up for review, merge it, push it out to where I was testing, and confirm it's fixed and we're good to go. I've been at this for 15 years so I know how to debug and eval fixes and whatnot, but Claude definitely found the issue quickly, proposed a fix, iterated on that fix when I wasn't as happy with it, and got it implemented in like...15 minutes? I've encountered plenty of juniors in my time who haven't really touched a debugger before, so while I can understand OP's frustration about how they're getting praise for shipping features quickly, I'm a little less with them on being miffed about juniors not being good at debugging. That's absolutely a skill that develops over time and reps.