Senior Engineer (12+ years) · Staff-Level Scope · Developer Experience · TypeScript/Go
Latest Posts
View all postsI Didn't Know What Was in My Context Window. So I Went Looking.
After installing gstack, I wanted to dig deeper than vendor UIs into what actually lands in context. I built Context Mate as a local experiment to unify traces across Cursor, Claude Code, and Codex. So far it is only partly successful: useful for coarse Cursor buckets and Claude token curves, but not a full inventory by name, and fragile on undocumented storage.
- AI Coding Agents
- Cursor
- Claude Code
- Context Engineering
- Developer Tools
If You Can't See the Boundary, You Can't Reason About the System
For App Router practitioners: React Server Components are not hard because the idea is hard. They are hard because the server and client boundary stays invisible at runtime. This post explains why that breaks reasoning, where Next.js dev tooling already helps and where RSC observability could go deeper (dev indicator, MCP), introduces RSC Boundary as the dev overlay I ship today, and sketches a constructive extension point so ecosystem tools could register inside the Next.js dev UI instead of separate chrome.
- Next.js
- React
- RSC
- Nuxt
- DevTools
The Hidden Complexity of Webhook Debugging
Webhooks look simple, but delivery guarantees, retries, and local tunnel workflows create subtle failure modes that waste engineering time. This post maps the real problems teams face and defines what a reliable debugging workflow should provide.
- Webhooks
- Developer Experience
- Observability