Open to Backend, GenAI & Full-Stack roles · remote or Hyderabad
// writing — 8 articles
What happened when we pressure-tested Tombstone v1.0 against production reality: a kill switch silently returning 400, approval endpoints wired to routes never registered, a scheduler that could double-fire. Nine bugs. Nine fixes. Here's the post-mortem.
How I built trelix — a zero-infra code intelligence engine that indexes any repo with Tree-sitter, runs 7-leg RRF retrieval, and answers questions about your codebase offline. From four hours of archaeology to a query that returns in 200ms.
How I designed Inkforge's generation engine — a STORM two-stage pipeline with explicit outline artifacts, in-process BM25 RAG (no vector DB), and Playwright-rendered LinkedIn carousels.
Why I spent months building a self-hosted feature flag intelligence platform instead of just using LaunchDarkly — the 2am incident that started it, the Knight Capital lesson, and how circuit-breaker auto-rollback works.
At scale, feature flags stop being booleans and become a distributed control plane — here's the architecture, failure modes, and operational patterns that make them work at millions of evaluations per second.
A packet-level walkthrough of what actually happens when you type www.google.com — DNS, TCP, TLS, HTTP, and rendering — with the latency costs and design trade-offs at each layer.
A systems-level walkthrough of DNS resolution — from browser cache to authoritative nameserver — covering record types, anycast infrastructure, GeoDNS, and the operational edge cases that bite engineers in production.