dmesg --follow
[ 68771580.000 ] posts.x: Full workshop on wiring Qodo's rules, skills, and local gates into a payments API refund task:  |   [ 68771580.000 ] posts.x: A refund endpoint that keeps its idempotency state in a process local dictionary isn't durable storage. That's the bug @nnennahacks, Principal…  |   [ 68764080.000 ] posts.x: Full talk on MiniMax's sparse attention design and why multimodality got trained in from the start instead of added after:  |   [ 68764080.000 ] posts.x: Most sparse attention designs look clean on paper and then run into real GPU memory access patterns. @olive_jy_song, RL Lead at MiniMax, works…  |   [ 68745180.000 ] posts.x: @nathanbenaich Isn’t he doing this? @AndrewYNg  |   [ 68698440.000 ] posts.x: Full talk on building and deploying MCP servers and agents with Spin and Akamai Functions, including the live cold start numbers:  |   [ 68698440.000 ] posts.x: Cold starts are the tax every serverless AI agent pays, and @ThorstenHans spends "Zero Cold Starts: Serverless AI Agents on Akamai Functions" trying…  |   [ 68692020.000 ] posts.x: Full talk on building a structured query engine for agent context, from schema discovery to self-correcting queries:  |   [ 68692020.000 ] posts.x: When Claude starts a task with no context attached, it behaves like a brand new employee: grepping through the codebase, guessing at what matters…  |   [ 68673720.000 ] posts.x: @davidsenra you will love this!  |   [ 68673600.000 ] posts.x: https://t.co/vhJifvV8y9  |   [ 68673600.000 ] posts.x: This Jay-Z documentary, In 8, is exceptional! Nearly 6 hours of intimate conversation between @sc and the brilliant @RickRubin. It’s rare to get such…  |   [ 68662260.000 ] posts.x: Full talk on turning re-prompted fixes into linters, including the OpenAPI drift fix and the skill-writing whack-a-mole:  |   [ 68662260.000 ] posts.x: Re-prompting an agent to fix the same sloppy pattern over and over isn't a workflow, it's a sign the rule should live in code, not in your head…  |  
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