Building tools that make developers faster. Frontend architect with a bias toward developer experience and productivity engineering.

I spend most of my time thinking about developer velocity — how to eliminate toil, reduce feedback loops, and build systems that help teams ship better code faster. Whether that's designing plugin architectures, optimizing build pipelines, or building frameworks from scratch.

Currently architecting monorepo infrastructure and implementing distributed tracing for frontend observability. Previously built framework tooling at Godspeed Systems and scaled engineering teams through acquisitions.

The best engineering leverage comes from multiplying other engineers' productivity. Great tools don't impose workflows—they remove friction and get out of the way.

I believe in:

• Listening before building — Most solutions already exist in the team's collective knowledge
• Systems over features — Build platforms that enable others to build faster
• Zero-config where possible — The best API is no API
• Type safety at compile time — Catch errors before runtime, always

Languages & Frameworks

TypeScript, JavaScript, React, Next.js, Node.js, Rust

Build & Infrastructure

Monorepo: Turborepo, Nx
Bundlers: Vite, Webpack, ESBuild, Turbopack
CI/CD: GitHub Actions, Docker, Terraform

Architecture

Design Systems, Micro-frontends, Component Libraries
State Management: Redux, Zustand
API: GraphQL, REST, WebSockets
Runtime: Deno, NodeJS

Observability & Performance

Grafana, FARO, Sentry, Distributed Tracing
Performance Profiling, Web Vitals, Lighthouse

Databases & Search

PostgreSQL, MongoDB, Elasticsearch

Streaming

WebRTC, HLS, Real-time Collaboration Systems

• Plugin architecture for auto-generating type-safe endpoints from OpenAPI specs — eliminated 70% of boilerplate code and entire class of runtime type errors
• Pluggable data source system with 100% TypeScript type compatibility — zero-config integration for 15+ data sources (PostgreSQL, MongoDB, Elasticsearch, Kafka, etc.)
• Live collaborative web IDE with real-time multi-user editing
• YAML-based dynamic form generator that integrates directly with framework daemons

• Monorepo architecture with shared component libraries — reduced build times by 40% and enabled code reuse across 4+ applications
• Distributed tracing implementation with FARO and Grafana — full request lifecycle visibility from browser to database

• Design systems that teams actually use (not just documentation that gets ignored)
• Video streaming platform using React, HLS, and WebRTC with adaptive bitrate streaming

Remote since 2018. Built strong async communication habits and documentation-first culture. Worked with distributed teams across India, Japan, US, and Europe.

Contributor, not gatekeeper. I review code to help improve it, not to assert authority. Best ideas win, regardless of who suggests them.

Pragmatic about tooling. Use the right tool for the job. Not religious about any particular framework or library. Will choose boring, proven tech over shiny new things unless there's a compelling reason.

• How to design APIs that feel obvious to use
• Why some tools get adopted and others don't (hint: it's rarely about features)
• Build systems and why they're always slower than they should be
• The tension between type safety and developer ergonomics
• Why documentation is code, not an afterthought
• How remote work changes what "productivity" means

• AI-powered code generation and its impact on developer workflows
• Bazel build system for large monorepos
• Advanced TypeScript patterns for better DX
• Deno and Firecracker MicroVMs
• Observability patterns for micro-frontends

• Building scalable frontend architectures
• Monorepo strategies and build optimization
• Developer experience design
• Framework design patterns
• Making build times faster (always happy to nerd out about this)

• LinkedIn: linkedin.com/in/itszero8
• Email: hello@zero8.dev

Open to interesting problems in developer tooling, frontend architecture, and engineering productivity.

"The best measure of a developer tool isn't how powerful it is—it's how quickly someone can forget it exists while getting work done."