Boredom, Anxiety, and the Anti-Flow Triangle

Identify what kills flow from inside — the boredom-anxiety-distraction triangle — and document a personal response protocol for each pattern. Walk away with an Anti-Flow Pattern Recognition Sheet you tape to your monitor. The anti-flow triangle is the exception-handling layer of the cognitive system. Rails has three relevant exception types: operations errors (boredom — the system is under-utilized and starts logging warnings about idle resources), capacity errors (anxiety — the system is over capacity and starts queuing or dropping requests), and external interrupts (distraction — a SIGINT from outside the application logic). All three are exceptions; the response to each is different. The boredom-killer pattern in engineering is well-known: when the work is below your skill ceiling, the prefrontal cortex disengages and the DMN takes over. The cognitive equivalent of an idle Rails worker is a mind that wanders to Hacker News. The fix is not "discipline yourself to focus on the boring work"; the fix is to raise the challenge level of the work — add a constraint (write it in a new style; use a less-familiar testing approach; refactor while you implement; time-box more aggressively). The same boring task, with one self-imposed constraint, becomes flow-eligible. The anxiety-killer pattern is the inverse: when the challenge exceeds your skill, the executive system over-loads and avoidance behaviors emerge. The fix is not "push through"; the fix is to lower the challenge appropriately — make the subgoal smaller, find a reference implementation, drop a dimension of difficulty (build with the feature broken in three places before fixing all three), or get a pair-programming partner. The new-language anxiety, if you are carrying one, is treatable by a smaller subgoal, not by more discipline. The distraction-killer pattern is the interrupt handler. Eyal's internal-trigger framework is structurally identical to identifying which interrupts in your system come from external sources (the network) vs. internal sources (a misbehaving thread in your own application). Most engineers spend years trying to silence the external interrupts (notifications, Slack, email) before noticing that 60–80% of their distractions are internal interrupts thrown by their own anxiety, boredom, or avoidance. Module 5's meditation practice trains the skill of noticing the internal interrupt before it propagates to a behavior. This module trains the skill of handling it.