> You can see in chats 11 to 14 that we're entering the slop zone. The code the agent created has a critical bug, and it's absolutely failing to fix it. And I have no idea how to fix it, either.
I'm glad to see rsc still actively involved. And commenting on commit messages.
The older I get the more I value commit messages. It's too easy to just leave a message like "adding valgrind support", which isn't very useful to future readers doing archaeology.
I'm coming to expect that most things you see on the internet are written by an LLM. I can't wait for all the de-LLM denoiser products that're sure to come out combating llm spam.
Thanks for bringing up therapy. I've been in therapy for some time, which lead to leaving my former position. I agree with you that my brain is certainly more buggy than my side projects :)
I've definitely done that as well. I generally don't have a problem with it, but it makes for an extra conversation the first time someone sees the pattern.
Given how some of the other ergonomic changes in go have gone (closures capturing loop variables, for instance), I'd support a change to lexical scoped defers if it were on the table.