Different stacks, different teams, one habit: ship what survives Monday morning. Every role below is real — see projects for the open-source side.
Lead the engineering org: architectural standards, code reviews, system-design calls, and mentoring across the team. Stay hands-on on the backend — NestJS services, queue and cache topology, observability, and the production systems behind them.
Backend-first on NestJS — REST + GraphQL surfaces, BullMQ workers for heavy jobs, Redis for cache + pub/sub, and WebSockets for realtime. Own MySQL/MongoDB schemas, GitHub Actions CI/CD, and Docker-based deploys to AWS. Ship the React/Next.js front-ends and Flutter mobile when needed.
Founded and run Teispace — building open-source developer tooling and shipping products end-to-end. Maintainer of the @teispace npm packages with ~4K monthly installs.
Mentored final-year students on capstone projects — API design, backend architecture, and shipping production-grade systems. Helped them bridge academic work to engineering practice with code reviews, deployment, and operational thinking.
Built backend services in Node.js + Spring Boot powering e-commerce and social platforms. Owned MySQL + Redis performance, shipped cross-platform mobile in Flutter, led code reviews, and designed GitHub Actions CI/CD pipelines.
Led planning, execution and delivery for software projects. Built backend in Java + TypeScript on Spring Framework with Spring Security; shipped cross-platform mobile in Flutter/Dart.
Built full-stack applications on Node.js + Express with Cloud Firestore / Firebase backing. Wrote backend Java services and shipped cross-platform mobile in Flutter while collaborating closely with the core team.
Scaffold a Next.js 16 app in one command.
An opinionated CLI that scaffolds Next.js 16 with TypeScript, Tailwind v4, Biome, Pino, Zod, Redux Toolkit, next-intl, and Vitest pre-wired. A manifest-driven `doctor` and `remove` keep installs in sync with the latest template.
Zero-flash theme manager for Next.js.
Drop-in replacement for the unmaintained next-themes. Zero-flash SSR, hybrid storage, view transitions, fully typed themes — none of which the original supports.
Production-ready Next.js template.
The reference template behind the next-maker CLI. TypeScript, Redux Toolkit, next-intl, Tailwind, and a full quality-gate pipeline shipped on day one.
Intercity ride-sharing for Nepal.
Three-app system — Flutter passenger app, Next.js admin, NestJS backend — connecting riders with vetted drivers for intercity routes. I led engineering: owned the backend end-to-end, mentored the Flutter and Next.js teams.
A digital library for Vedic rituals.
Three-app product — Flutter mobile app, Next.js web reader, Node.js backend — curating Dharmasastra and Karmakanda texts in Sanskrit, English, and Nepali. I owned the backend solo and supported the mobile and web teams on integration.
Most of the work doesn't ship — it accumulates. The numbers below come straight from the source, not a frozen screenshot.
Written in Nepali, mostly at night. Some I sing; some sit on the page until they're ready. They're not separate from the engineering — they're the same instinct, in a different language.
Adding smooth scroll to a Next.js site is one of those changes that feels free for the first hour and then breaks half your layout. Here is the catalogue of what breaks and how to fix each one.
Most Next.js teams keep starting from broken templates. So I built a CLI that ships an opinionated stack with TypeScript, Tailwind v4, Biome, Pino, Zod, Redux Toolkit, and a manifest-driven doctor — in one command.
A custom GLSL portrait, a real audio engine driven by AnalyserNode, and a 24-command zsh-style terminal with a virtual filesystem. Here is how the pieces fit, what broke, and what I would do differently.
