✳flâneur — a map of the web's best reading
RL Pet Peeves Part 1 · Auriel
aurielws.github.io · 3,448 words · saved by 2 readers
My personal do's and don'ts for startups post-training their own model. A guide to trajectory eyeballing, harness debugging, and RL failure modes.
RL Pet Peeves Part 1 · Auriel This mini-series is a collection of rants on RL from my POV. Pure, unfiltered, first-person opinions from someone who's spent years deep in the trenches of pre-training, post-training/fine-tuning, inference time, and every layer of the stack for models from small distilled models (Pixel Real Tone base model) to frontier systems (Gemini + Nano Banana + Human Detection Models that powered Google Search, Waymo, Vertex AI). I've eyeballed thousands of trajectories, judged parametric wins and losses until my eyes bled at 2AM, and sat through more "data" pitches
Explore this link on the map →saved by
related reading
- Demystifying evals for AI agents \ Anthropicanthropic.com
- Debugging Reinforcement Learning Systemsandyljones.com
- Composer2.pdfcursor.com
- Reward Hacking in Reinforcement Learning | Lil'Loglilianweng.github.io
- Your AI Product Needs Evals – Hamel's Blog - Hamel Husainhamel.dev
- Agent Observability and Tracingarize.com
- Discovering Language Model Behaviors with Model-Written Evaluations — LessWronglesswrong.com
- The bitter lesson of LLM evalsparsed.com
- Agent Evaluation: A Detailed Guidecameronrwolfe.substack.com
- Features as Rewards: Using Interpretability to Reduce Hallucinationsgoodfire.ai
- Lecture 01. Strong Models Don't Mean Reliable Execution | Learn Harness Engineeringwalkinglabs.github.io
- confessions_paper.pdfcdn.openai.com