2026-03-03 · Lab Notes ◆ Experimental
Zen and the Art of Vibe Coding
Infinite capacity creates infinite anxiety. An operating protocol for managing both.
Build anything
Intoxication
⇆
Never enough
Paralysis
This tension defines high-leverage builders in 2026. It compounds daily. The only counter is designed boundaries.
The Protocol
$ --rule build at the workstation, nowhere else
Major projects require full context. Phone builds fragment attention and open loops you can't close until you're back at the desk.
$ --rule one screen = one project, no exceptions
| Screen | Project | Scope |
|---|---|---|
| 1 | Flow Education | React app, curriculum, student UX |
| 2 | StoryBook Studio | Marketing, content, operations |
| 3 | Lab Notes | Articles, skills, research |
| 4 | Infrastructure | APIs, model eval, prototyping |
$ --rule away from desk = inputs only
Research. Writing. Planning. Things that refill. Choose what excites you, not what obligates you.
$ --rule phone activity-matched
| Context | Allowed | Blocked |
|---|---|---|
| Walking | Research, reading, audio | Building, generating |
| Social | Quick notes, status checks | Anything that pulls from conversation |
| Transit | Drafts, review, light comms | Deep work, debugging |
$ --rule two hours offline, daily, non-negotiable
Queue agent tasks. Document states. Set DND. Walk away. Agents run without you. You recover without them.
Target 2h/day
Mode No screens
Prep Queue agents before exit
Outputs
Context enforcement — screens and locations do the work, not willpower.
Closed loops — projects built or paused, never hanging.
Designed recovery — deliberate absence, not accidental downtime.