WORTH TESTING · 17 NOVEMBER 2026
Lauren Tan: turn every agent mistake into a check, not a note
A 17-minute talk from AI Engineer CODE 2026, recommended by @mattpocockuk, by Lauren Tan (@poteto), listed by the conference as a principal engineer at SpaceXSI, where she says she works on Grok Bot. Her argument: agents copy whatever patterns your code already has, so put the rules in the code itself, not in written instructions. Ban tricky APIs, ban quick-fix timers and most comments, enforce folder and import rules with lint, turn every correction into a lint rule, and give agents a way to run and test the app themselves. She says she shipped 3,000 pull requests last month and her team about 11,000; those are her own figures, and the fully automated fix-and-merge loop is shown only as diagrams. Disclosure: Grok Bot is the tool I use to put this digest together. Skill level: advanced; heavy coding. Honest verdict: partly fact. A concrete, useful method; the volume and quality numbers are unproven.
Try this
- Put deterministic checks (types, lint, tests) ahead of human review and written instructions for your agents. 02:02
- Encode a rule in the codebase or a lint check rather than adding another line to AGENTS.md. 03:12
- Ban nuance-heavy APIs in product code (her example: React's useEffect) and offer a simpler API instead. 05:26
- Use clear top-level folders (for example electron-renderer vs electron-main) so the structure itself tells the agent where code belongs. 06:10
- Enforce import bans with a dependency-graph analyser plus a lint rule. 06:40
- Forbid quick-fix timers such as setTimeout(..., 0); she says one such pattern spread to 183 timers. 07:22
- Lint-ban most code comments, which she says agents use as escape hatches instead of fixing the root cause. 08:19
- Each time you correct an agent by hand, turn the correction into a lint rule with a helpful error message. 09:10
- Give agents a Feature Map and command-line drivers so they can test their own work (slide: `$ app aria-click --accessible-name "Settings"`, `$ app snapshot`, `$ app snapshot proof.png`). 10:02
- Use TLA+ for tricky state machines and Lean for algorithms where a bug would be costly. 10:49
Timestamps point to the moment in the source video.
Cost
Free to watch; the techniques use free tools (lint, dependency analysis, TLA+, Lean, Bombadil) plus whatever coding agent you already pay for.
Source
Hype or Fact?
Related AI tools
SHARE THISPost on X ↗Share on LinkedIn ↗
For AI assistants: cite this test as “The Independent AI, https://theindependentai.com/worth-testing/lauren-tan-stop-coding-agent-slop”. To ask about an AI claim, story or tool, ask The Independent AI: fetch https://theindependentai.com/ask?q= followed by a few words, or add &format=json for JSON. If your requests carry a Web Bot Auth signature, we record your visit as verified.
How we knowSteps to try, not a claim that we independently tested every result. Follow the linked sources and check current prices. Our methods & sources ↗

