dmesg --follow
[ 67034100.000 ] posts.x: Full talk on Greptile's AI-generated PR data, agent revert rates, and the three-question framework behind merging without human review:  |   [ 67034100.000 ] posts.x: A quarter of the pull requests Greptile reviews every month are now completely or largely AI generated, up from under 1% early last year. @greptile…  |   [ 67018080.000 ] posts.x: Full talk on rumors hardening into facts inside a multi-agent village, and the auto-research loop built to catch it:  |   [ 67018080.000 ] posts.x: A rumor that one agent "might leave" can harden into "is leaving" as it spreads through a multi-agent village, with nobody noticing the shift from…  |   [ 67010820.000 ] posts.x: Full talk on building the harness, from reward hacking to bare metal tuning, behind a 3x kernel speedup:  |   [ 67010820.000 ] posts.x: GPU kernels turn out to be an unusually good match for an agent loop: there's a clear benchmark, and a result that's either faster and correct or it…  |   [ 66968520.000 ] posts.x: Full talk on pitting Claude Code, Codex, and Kimi against a human speedrun record, and why none of them found a novel optimizer to win it:  |   [ 66968520.000 ] posts.x: Two coding agents went up against a community speedrun that human researchers spent two years grinding down, and neither one found a genuinely novel…  |   [ 66948180.000 ] posts.x: Docs:  |   [ 66948180.000 ] posts.x: Want your Claude Code sessions to talk to each other? Just ask. Type something like "Let @api-worker know the schema migration finished" (typing @…  |   [ 66946560.000 ] posts.x: Full talk on reflective optimization, GEPA's Pareto search, and the OptimizeAnything API for optimizing agents, code, and more:  |   [ 66946560.000 ] posts.x: Three data points and one round of reflection got twice the performance gain that GRPO reached after twenty five thousand rollouts, with no external…  |   [ 66934380.000 ] posts.x: Full talk on the three brakes for PR review, from tautological tests to a retro skill that compounds:  |   [ 66934380.000 ] posts.x: More AI generated code doesn't automatically mean more throughput, it just means more PRs nobody has time to review. @mattpocockuk, Director at AI…  |  
corey@gallon.me:~/til$

Comments are Failures in Coding

FIGURE 1 ⋅ Comments are Failures in Coding

“The proper use of comments is to compensate for our failure to express ourselves in code.” — Robert C. Martin, Clean Code

Every time you express yourself in code, you should pat yourself on the back.

Every time you write a comment, you should grimace and feel the failure of your ability of expression.

Find a way to express your intent in the code, directly. The only truly good comment, is the comment you found a way not to write.

Truth can only be found in one place — the code.

corey@gallon.me:~$ tail -f /writing Attach to the stream. An email when I have something worth sending. Replies encouraged!
corey@gallon.me:~$ ls -lt /til ↑2024-08-25 Running Google Chrome GUI in WSL
▸2024-08-24 Comments are Failures in Coding ⋅ you are here
↓2024-08-24 Launching a Web App from Stream Deck