chrsig

the narrow window view is appreciated given the increased indent level of your comment

> 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.

This definitely relaxes my ai-hype anxiety

to be useful to whom, exactly?

w.r.t. your edit: Is there anything the community at large can do to aid your efforts?

You're sort of answering your own question. It was a matter of proximity. The thousand others were a greater distance in the initial conditions.

valgrind finds sooooo many more problems than just memory leaks

uninitialized memory, illegal writes, etc... There's a lot of good stuff that could be discovered.

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.

Useful for people -- believe it or not not all of us internalize the language we use as part of our identity (and species).

From someone that grew up in New England, but experienced a 4.x in california: I assure you it does not feel small.

The revelation that the ground does not stay where I left it was quite disturbing.

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 :)

Think of it like emacs. Browsers are perfectly good operating systems just needing a better way to view the web.

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.

yeah, I've always just extracted the loop body into a new function as a result