Notes written in the field are good at recording results and reflections, but keeping the flow that led to those results as structure is surprisingly hard. The procedure that lived only in someone's head at the time, the implicit assumptions that didn't make it onto the page, the judgment calls that got summarized away in meeting decks — when you read the notes back years later, those rarely survi
TL;DR I try to keep my eyes on the AI agents. I gave one too much rope once, and the kind of mess it made while I wasn't watching is something I'd rather not retell. Which is why I needed 5 monitors. To run 5 agents in parallel, 5 VSCode windows have to live in one field of view. Physical monitors hit a wall. No desk fits five; even my viewing angle gives out before the desk does. So I strappe
I wanted to ask AI about it, but the flow was annoying: switch to a browser, open a chat tab, copy or type the error, wait for an answer, then switch back. After doing that too many times, I started building something that works directly on the desktop. That became Xerolas. Xerolas is an AI screen lens for your desktop. It works like this: Press Ctrl + Shift + Space Drag over any region of your
Lately, I’ve been reflecting on something: The question for most developers is no longer "Are you using AI?", but rather "How and why are you using AI?". I’ve noticed AI tooling becoming increasingly embedded in my daily workflow. At this time last year, my usage of AI was limited to code autocomplete suggestions in my IDE that I would manually validate. Now I am using coding assistants to help id
I spent a weekend connecting every MCP server that sounded useful. By Sunday night I had 11 running, a claude_desktop_config.json that scrolled off the screen, and an agent that was technically capable of doing almost anything. In practice, it was doing almost nothing useful. What I learned had very little to do with which servers are "good." The MCP ecosystem has exploded. There are directories w
It works on any React or TypeScript component — hooks, utilities, classes — and generates a props table, README section, and a complete Storybook story file in about 10 seconds. Not a big story here. I was documenting a component for a design system at work and spent about 15 minutes cleaning up what Claude gave me. Structured it into a proper props table, extracted the Storybook argTypes, reforma
Most agency onboarding fails before the kickoff call happens. Not because the team isn't good. Not because the client is difficult. Because nobody collected the right context upfront, and the kickoff call becomes the place where everyone discovers what they don't know yet. The intake form is the fix. Not a 3-question "tell us about your project" form. A real one. Here's the framework we use — 27 q