Debugging is more important than features
My blog returned 404 on every page at 2 AM. I had zero visibility into why. Here is the debugging infrastructure I wish I had set up from day one.
Full-stack contractor. Payments and billing integrations, AI agents that survive production, and end-to-end product builds. Remote, UTC+1
Stripe and beyond: subscriptions, metered billing, webhooks that don't drop events, and migrations that don't double-charge anyone. The edge cases other people skip
Not a demo. Agents with real context, guardrails, observability, and a token budget. Built to run reliably against your data
Owning a build end to end: architecture, infra, frontend, the lot. Pragmatic over perfect. I optimize for what you can maintain after I leave
I spent 2 weeks making my serverless functions clean. The architecture was wrong. I rewrote everything as a single Express server and it was simpler.
My blog returned 404 on every page at 2 AM. I had zero visibility into why. Here is the debugging infrastructure I wish I had set up from day one.
I spent 3 hours reviewing a 200-line PR that handled every edge case. A 40-line version with a TODO would have been better. Here's why perfect code slows you down.
Stripe is the default answer for online payments. But if you only need one payment method, you're paying for features you'll never use. Here's what I found when I actually compared providers.
How to handle Open Graph meta tags for LinkedIn, Google, and Discord previews in a React SPA using server-side user-agent detection with nginx or .htaccess.
How to generate a smart summary of branch diffs. Highlights deleted files and renames to give AI agents the context they need to review, refactor, or document code.
How to test AWS Lambda functions and EventBridge rules locally using SAM, LocalStack, and docker-compose. No cloud deployment needed.
I asked AI to generate Terraform for a standard AWS setup. It produced 2,400 lines that worked perfectly. Here's why I'd never deploy it to production.
How to verify the actual context window of an LLM, understand external vs internal context, and avoid the silent truncation problem.
How loom-memory turns a Git repository into a persistent knowledge base for AI agents. Reduce token spend by giving models durable context instead of cold reads.
Payments and billing, AI agents in production, or owning a full-stack build end to end. Remote, UTC+1. 20 minutes is enough to know if it's a fit