Atharv Dange - Full Stack Engineer & Cinephile
█████╗ ████████╗██╗ ██╗ █████╗ ██████╗ ██╗ ██╗ ██╔══██╗╚══██╔══╝██║ ██║██╔══██╗██╔══██╗██║ ██║ ███████║ ██║ ███████║███████║██████╔╝██║ ██║ ██╔══██║ ██║ ██╔══██║██╔══██║██╔══██╗╚██╗ ██╔╝ ██║ ██║ ██║ ██║ ██║██║ ██║██║ ██║ ╚████╔╝ ╚═╝ ╚═╝ ╚═╝ ╚═╝ ╚═╝╚═╝ ╚═╝╚═╝ ╚═╝ ╚═══╝
██████╗ █████╗ ███╗ ██╗ ██████╗ ███████╗ ██╔══██╗██╔══██╗████╗ ██║██╔════╝ ██╔════╝ ██║ ██║███████║██╔██╗ ██║██║ ███╗█████╗ ██║ ██║██╔══██║██║╚██╗██║██║ ██║██╔══╝ ██████╔╝██║ ██║██║ ╚████║╚██████╔╝███████╗ ╚═════╝ ╚═╝ ╚═╝╚═╝ ╚═══╝ ╚═════╝ ╚══════╝
Full Stack Engineer building production systems end-to-end, from auth protocols and API design to the interfaces people actually use.
$cat about.md
I'm a Full Stack Engineer based in Pune, India. I build production systems end-to-end - from auth protocols and API design to the interfaces people actually use. I'm also the co-founder of SpaceBuilder (opens in new tab), where we build custom software, AI automations, and web applications for businesses.
When I want to understand how something works, I rebuild it from first principles. I've built HTTP frameworks, client-side routers, CSS engines, OIDC providers, and web rendering pipelines - not to replace existing tools, but to understand the problems they solve at the protocol level.
Outside of code I write about what I find at blog (opens in new tab) and watch way too many films.
$cat experience.md
- ▸Co-founded an IT services startup building custom software, AI automations, and web applications for businesses
- ▸Leading technical direction - scoping projects, architecting solutions, and shipping client work end-to-end
- ▸Building workflow automations and AI systems that replace manual processes with engineered solutions
- ▸Built and shipped production products end-to-end across the full stack
- ▸Took ownership of the IT department - architecture decisions, client-facing project scoping, quotations, and on-time delivery
- ▸Mentored interns and junior developers
- ▸Conducted technical interviews for new hires
- ▸Entered a profit-share agreement reflecting expanded ownership and responsibility over the firm's technical direction
$ls projects/ --featured
Built a production-grade OpenID Connect identity provider from scratch - implemented the OAuth 2.0 Authorization Code Flow with PKCE, RS256 asymmetric JWT signing, automatic refresh token rotation with theft detection, and shipped a plug-and-play Next.js SDK for client apps.
A beautifully crafted, read-only GitHub dashboard for Android. Browse repos, explore code, track your contribution streak, and share your profile - without the pressure of taking action.
Built a zero-dependency HTTP server framework from Node.js core modules - designed a compile-time type-safe router with parameter inference, an async onion-model middleware pipeline, and built-in rate limiting, CORS, CSRF protection, and Brotli compression. Published to npm.
A production-grade web crawler and sitemap discovery engine with background job processing, real-time progress streaming, and intelligent CSR/SSR detection for creating SEO-compliant XML sitemaps.
$cat stack.md
$ls blog/ --recent
A concept by concept walkthrough of what happens inside a modern LLM: tokenization, embeddings, RoPE, attention, induction heads, multi-head attention with GQA, the feed-forward network, residual streams, and next-token prediction. Written up after working through the mechanics until every piece made sense.
Two slices that teach the rest of the system to read the route tree slice 8 turned into the single source of truth. Slice 9 makes the type system check every path and param at compile time. Slice 10 replaces order-dependent first-match matching with a specificity score, so the right route wins no matter how the tree is written.
Two slices, one underlying idea: stop hand-maintaining information that already lives somewhere else. Search params turn the URL into a typed, first-class data source instead of a string every component re-parses. Codegen turns the routes folder into the single source of truth for the route tree, instead of a hand-wired array someone has to keep in sync by hand.
Two problems that show up once a router has real users hitting it: what happens when one route breaks, and what happens while a user is deciding whether to click. This post covers building per-route error boundaries with two separate error channels, and prefetch on hover that reuses the exact same loader pipeline instead of building a second one.