Writing
Field notes on the tools, stacks, and builds I ship — curated from what I share on LinkedIn.
7 Articles
You sped up the one loop that was never the problem. Andrew Ng's diagram explains it perfectly: building software with AI runs on three loops, and they move at completely different speeds — minutes, hours, and days.
The big logic, the complex features — AI handles those beautifully. The margins, the widths, the spacing? A nightmare. Here's a free tool that fixes it: click the element, leave a note, and your AI agent knows exactly what you're pointing at.
Most people nod along. Very few can actually explain them. The cheat sheet I wish someone had handed me when I started shipping with AI — no jargon, no fluff, just the 12 terms that actually come up.
A single CLAUDE.md file gets you started, then quietly becomes the ceiling. Here's the directory structure I actually run — context, rules, commands, skills, agents, and hooks — and the two pieces that make multi-developer work with Claude Code collision-free.
Not a static chart, not a table of numbers — an actual 3D map where you watch the water move, the Indus glow brighter on a high-flow day, and the dams rise and fall with real reservoir levels. Built in a day with Claude, deck.gl, and live hydrology data.
If you're using OpenAI Codex seriously, you've probably hit this wall: multiple accounts, each with its own 5-hour and weekly limits, and the only way to check any of them is to log in and run /status. Here's how I fixed it with a small local Python dashboard.
AirPods have an accelerometer and a gyroscope streaming head-orientation data all day, and almost nobody reads it. I spent a weekend building a macOS app that does — and found a live breathing-rate monitor hiding in the same signal.