| ▲ | bakugo 13 hours ago | ||||||||||||||||||||||
Recently, I was browsing through commits on a tool I use, to evaluate how AI-slopped it had become, and came across this absolutely amazing sentence that took me several passes to interpret, courtesy of Fable: > The wrapper is the try/finally seam future entry-condition changes need without re-indenting the loop. So this is definitely not an Opus-specific issue, as some people seem to believe. https://github.com/phpstan/phpstan-src/commit/934432a1b5007f... | |||||||||||||||||||||||
| ▲ | preg_match 8 hours ago | parent | next [-] | ||||||||||||||||||||||
This is why I reject agentic workflows and, in fact, do not let Claude perform commits at all. I remain in control of Git completely and read all the diffs. Also, in my experience, agentic flows are just bad. They seem like a productivity gain until you notice that it uses 100x more tokens, and therefore more time. I can prompt and read answers faster. | |||||||||||||||||||||||
| ▲ | mort96 13 hours ago | parent | prev [-] | ||||||||||||||||||||||
I actually can't read this. > The statement-list walk without the per-list pending-fiber flush "Per-list pending-fiber flush?" Surely there's a clearer way to express this? Was it helpful necessary to describe "the statement-list walk" as a noun instead of talking about "walking the statement list"? > A pure move: processStmtNodesInternalWithoutFlushingPendingFibers() becomes a delegating wrapper and the loop body is byte-identical Did this need to be prefixed by "A pure move"? Why does the bytes of the text content of the loop body matter? I found this too: https://github.com/phpstan/phpstan-src/commit/a9260cb3584854... > Parked fibers are idle workers, not pending work - skipping their no-op fuel starves nothing. "No-op fuel"? Really? | |||||||||||||||||||||||
| |||||||||||||||||||||||