this is bizarre on many levels. you initially traced the cause to the CEO and _banned him_?
> This kind of error has bitten me before, far before LLMs were around. But this problem is exacerbated by LLM coding agents. A human doing this refactor would select the original text, cut it, move to the new file, and paste it. Any changes after that would be intentional.
huh! it's almost like a human SHOULD make that change...
> // Log error but continue with other installations
was this comment also written by LLM? if so, maybe simply stripping comments from the codebase the LLM works on would help? I've not studied enough if comments are more helpful or toxic for context. I do know that they rot...
Actually, i bet they were the cause, and they shouldnt have been. I bet the ceo has some super cow power permissions that let them see every repo, leading to querying the entire db
this is bizarre on many levels. you initially traced the cause to the CEO and _banned him_?
> This kind of error has bitten me before, far before LLMs were around. But this problem is exacerbated by LLM coding agents. A human doing this refactor would select the original text, cut it, move to the new file, and paste it. Any changes after that would be intentional.
huh! it's almost like a human SHOULD make that change...
> // Log error but continue with other installations
was this comment also written by LLM? if so, maybe simply stripping comments from the codebase the LLM works on would help? I've not studied enough if comments are more helpful or toxic for context. I do know that they rot...
So the CEO was a red herring? Just a timing coincidence?
I'd love for "the CEO logged in" to be somehow part of the root cause...
Actually, i bet they were the cause, and they shouldnt have been. I bet the ceo has some super cow power permissions that let them see every repo, leading to querying the entire db