Workflow Discipline

• Abandon the habit of letting coding agents approve their own work; implement a strict separation where a fresh conversation acts as a reviewer to eliminate self-confirmation bias.14:27
• Stop using "slash compact" commands to manage context windows, as studies suggest only 10% of technical details survive summarization; prioritize smaller work units and handoff documents instead.4:13
• Treat validation as a system by planning testing and edge-case checks before code is written, rather than treating them as after-the-fact verification steps.16:21

Controlling Agent Behavior

• Replace probabilistic, instruction-based rules for critical tasks with deterministic "hooks" that trigger mandatory actions, such as running tests after implementation.5:33
• Audit global rule files frequently to prevent "rule drift," where outdated instructions about file paths or dependencies conflict with the current codebase; keep these files under 300 lines to avoid context bloat.2:54
• Avoid escalating to larger models mid-task when a session becomes unreliable, as the existing conversation context is already tainted by embedded errors; "burn it to the ground" by creating a handoff document and starting a fresh session.11:19

Complexity and Constraints

• Shun complex multi-agent coordinator frameworks, which the speaker argues are experimentally unreliable, in favor of a single main agent acting as a simple delegator.13:10
• Limit parallel sub-agent usage, as excessive fan-out consumes tokens rapidly and may contribute to hitting rate limits without a proportional gain in output quality.9:53
• Resist the urge to over-revise code; studies indicate that after 10 to 20 iterations, early versions of the output are statistically more likely to be superior to the final, over-polished version.15:27