The archive, mapped
Every blog post and case study on the site with the principles and playbooks each piece argues for. Filter by any principle or playbook to see just the evidence behind it.
Matching the filter
7 items- A One-Page AI Usage Policy That Actually WorksApr 20, 2026 · 4 min
A short, adoptable AI usage policy for engineering teams: what to put on the page, what to leave off, and why the policy matters less than the habits it makes explicit.
- The First 90 Days: Introducing AI-Assisted Dev to a New TeamApr 20, 2026 · 8 min
A 90-day rollout for AI-assisted development: start with bounded habits, measure the work, and standardize only after the team has evidence.
- Build Your Own Legs Before the Crutches FailMar 9, 2026 · 13 min
How I use AI drafts to build engineering judgment through inspection, regression tests, code review, and repeatable release checks.
- Repo Design Patterns for AI-Assisted Dev: Control Loops, Hooks, and MemoryFeb 9, 2026 · 6 min
Treat the repository as a control system: versioned instructions, explicit workflows, fast hooks, durable context, and visible failure states.
- Loom: One Registry, Many AI Coding AssistantsFeb 9, 2026 · 7 min
How Loom generates and checks MCP configuration across nine client profiles from one canonical registry.
- Loom Mode: One Proxy, One Daemon, Faster MCPFeb 9, 2026 · 7 min
How Loom keeps MCP tooling predictable with one client entrypoint, daemon-owned process lifecycles, bounded output, and coarse-grained tools.
- Building Practical AI AgentsNov 15, 2025 · 5 min
A source-backed guide to agent reliability: explicit state, bounded tools, verification gates, and visible failure.