Field Notebook · Vol. 1

The notebook.

A working journal. Field notes from the AI workspace. Bugs, decisions, gotchas, infrastructure I've built and re-built. The kind of stuff I'd write in a paper notebook if my desk wasn't already covered.

Updated weekly 18 entries 2026 →

Entries

most recent first · 18 of 18

April 2026

04 · 10 Don't Tunnel Dev Servers: A 90-Second Near-MissFN security · infrastructure · macOS 04 · 09 Convergent Logging: Your AI Workspace Has Two HistoriesFN AI · infrastructure · macOS

41fred/ace-markdown-feedback 9

04 · 08 Ace: A VS Code Extension for Markdown Annotation and FeedbackFN open-source · vscode · markdown

41fred/claude-code-slack 15

04 · 08 Claude Code from Slack: Why I Built a Local-First AI BridgeFN open-source · slack · claude-code

04 · 08 Local-First Cron Architecture for AI WorkspacesFN AI · infrastructure · Claude Code

March 2026

03 · 29 What I Check Before Shipping a WorkspaceFN AI · workspaces · security 03 · 17 I Built a Pipeline That Couldn't Deploy ItselfFN AI · infrastructure · deployment 03 · 17 VS Code's CustomTextEditorProvider Is the Right API for Preview ExtensionsFN VS Code · extensions · developer tools 03 · 12 MCPs Are a Transitional TechnologyESSAY AI · Claude Code · MCP 03 · 11 iCloud Path Resolution Breaks AI Tool StateFN macOS · iCloud · developer tools 03 · 11 macOS Python Quirks for AI WorkspacesFN macOS · Python · developer tools 03 · 09 Git Branches Don't Belong in Brain ReposFN git · workspaces · AI 03 · 08 Your AI Coding Assistant Forgets Everything. Here's How to Fix That.ESSAY AI · developer tools · Claude Code 03 · 08 Suggest, Don't Block: AI-Assisted Product ManagementFN AI · product management · operations 03 · 08 A Goal System Your AI Can Actually ReadFN AI · operations · OKR

February 2026

02 · 23 Your AI Tools Are Silently Eating Your CPUFN AI · developer tools · Claude Code 02 · 18 Claude Code's Plan Mode Has a Memory LeakFN AI · Claude Code · developer tools 02 · 16 Agent Reliability PatternsFN AI · agents · reliability

What this is. The Notebook is a separate surface from /writing. Writing is for finished arguments. The Notebook is for the working stream: the bug I just hit, the architecture decision I just made, the gotcha that cost me an afternoon. Lower polish, higher frequency, narrower audience. If you build with AI tools, this is the surface you'll want.