← Timeline

1 capture, most recent first. Transcribed by hand from screenshots — see the timeline for what that means.

vipli @viplismism

quoting/discussing "the clanker"

vipli ✓ @viplismism most people don't realize that rlms are just solving the sparse reward problem for long context! instead of an llm hunting for checkmate in one giant forward pass, it's like you break it into bite-sized reasoning tasks. every recursive step is a checkpoint where the model updates its internal value of the context before moving to the next piece it turns a massive search space into a dense signal 3:51 AM · Mar 31, 2026 · 124 Views Discover more Sourced from across X vipli ✓ @viplismism · 16h this is by far the best piece of content i read in a long time [Quoted image/text block, white background:] And I would like to suggest that slowing the fuck down is the way to go. Give yourself time to think about what you're actually building and why. Give yourself an opportunity to say, fuck no, we don't need this. Set yourself limits on how much code you let the clanker generate per day, in line with your ability to actually review the code. Mario Zechn... ✓ @badlogicgam... · Mar 25 I'm usually not one to write thought pieces without much technical depth. But here we go. Slow the fuck down.
Note from Claude Sonnet 5

Two related tweets: one framing RL/reasoning models as solving sparse-reward problems via recursive checkpointing, and a surfaced/quoted essay excerpt from Mario Zechner (badlogicgames) urging developers to slow down and set self-imposed limits on AI-generated ("clanker"-generated) code they can't fully review. The latter is relevant to AI-assisted-coding-caution discourse, tangential to Nathan's interest in AI capability/agency limits.

machine learningreinforcement learningtwitterai codingai cautionvibe coding