Kishan Vaghani

Kishan Vaghani founded ShareCode and writes the engineering deep-dives on this blog. Day to day he ships product code on the Next.js front-end, the Firebase backend (Auth, Firestore, Realtime Database), the Yjs-based CRDT sync layer, and the WebRTC pipeline that runs voice and video for live pair-programming sessions inside the editor.

He holds a B.E. in Information Technology and worked in full-stack JavaScript before starting ShareCode — the usual progression of dashboards, then real-time dashboards, then realising most of the interesting bugs in his stack lived in the sync layer. ShareCode started as a weekend project to fix the latency and feature problems he kept hitting in other collaborative editors. It has been running in production long enough that the posts on this site quote behavior from real users rather than synthetic benchmarks.

The posts he has shipped here are: the WebRTC architecture explainer (SDP, ICE, STUN/TURN, signaling), the Firebase Authentication internals deep-dive (JWT structure, refresh-token flow, persistence modes, custom claims), the real-time sync walk-through (Yjs, state vectors, WebSocket transport), the technical-interview guide, the beginner intro to remote pair programming, and a couple of shorter teamwork posts. Most run 11–16 minutes of reading time, with full code examples and the specific production mistakes the team has hit and recovered from.

His writing focuses on the gap between a working tutorial and code you would actually ship. Most posts on the wider internet teach the happy path: fetch a token, render a list, connect to Firebase. His posts pick up at the failure modes — what breaks when the refresh-token loop has been silently broken for a month, why your video calls work in dev and fall apart with a fifth participant, how a security rule that passes a smoke test still leaks data under a real query pattern.

Outside ShareCode, Kishan reviews technical interviews using the platform, mentors developers earlier in their careers, and reads more distributed-systems papers than the size of the team strictly justifies. You can find his code on GitHub at github.com/kishanvaghani and reach him on LinkedIn at linkedin.com/in/kishanvaghani.

Most developers hit a tutorial after the obvious approach already failed. The job of the post is not to repeat the official docs — it is to build the mental model that lets the reader predict the next problem on their own.

Every engineering post here follows the same pattern. Start with the concrete symptom: the actual console error, the actual Firebase rejection, the actual failure that brought you to a search engine. Build up the model layer by layer until the symptom becomes obvious. Then offer the fix, with the trade-offs you accept when you adopt it. The format takes longer to read than a copy-paste recipe, on purpose — the goal is to leave you able to handle the next variant of the problem without searching again.

Born and based in Gujarat, India. Studied Information Technology (B.E.) and worked through the standard full-stack JavaScript path — dashboards, CRUD APIs, then a real-time dashboard that taught him most of what he now knows about state synchronization, mostly by debugging it at 3 a.m. before a customer demo.

ShareCode came out of frustration with existing collaborative coding tools — heavy installs, enterprise pricing for basic features, and latency that fell over the moment users joined from low-bandwidth connections. The first version was a weekend prototype. It has since grown into the product the engineering posts on this site reference directly.

Most engineering time right now goes into the WebSocket sync layer at higher participant counts — the architecture that handled two or three concurrent editors comfortably starts to behave very differently when an interview panel of five plus the candidate all join one room with screen share and voice on. The posts on this site will continue to track that work as it lands in production.

Writing-wise, the next posts in the queue are a deep-dive on how the editor handles offline edits and re-syncs after a dropped connection, a follow-up to the Firebase Authentication post covering the App Check and reCAPTCHA Enterprise migration, and a short retrospective on the architecture calls that did not age well.