The people behind the ShareCode blog
Every article on this site is written by a working developer or educator. No ghost-written posts, no AI dumps, no anonymous bylines. Here's who writes what, and what they actually know about.
Kishan Vaghani
Founder & Lead Engineer, ShareCode
Surat, Gujarat, India
Founder of ShareCode. Writes the engineering deep-dives on this site — WebRTC, Firebase Auth, real-time sync, and the production patterns behind the editor itself.
Writes about
Latest
How a Ronaldo Match Streams to 100 Million Screens: Live Sports Streaming Architecture
Kajal Pansuriya
Developer Educator, ShareCode
India
Developer educator at ShareCode. Writes the tutorial track — Python, JavaScript debugging, coding-interview prep, and the everyday code-quality habits that hold up in real codebases.
Writes about
Latest
Building a Football Stats Dashboard: React, Firestore, and a Football API
How we write, and why it matters
Six principles that shape every post on this site — from topic selection through review to long-term maintenance.
Every byline is a real person
No house pseudonyms, no AI-generated personas. Every post is signed by someone who can be reached and who stays responsible for the claims it makes. Click any byline to land on a full profile with bio, links, and the writer's complete catalogue.
Topics come from real work
Engineering deep-dives come from problems hit while building ShareCode in production. Tutorials come from questions developers ask repeatedly in mentorship sessions and support threads. We don't write to keyword volume.
Every post is reviewed
A draft moves through technical review (does the code actually run as described?) and editorial review (is it readable, honest, and free of accidental misleading framing?) before it ships. Most drafts come out of review shorter than they went in.
The team stays small on purpose
Two authors today, not twenty. Keeping the team small means each byline carries weight and the catalogue stays predictable. As the team grows we'll keep this page honest — real bios, real backgrounds, real lists of what each writer has shipped.
Posts age slowly
Substantive updates after publication get a fresh date and a note about what changed. Each post is treated as something we expect to be useful for years, not as content for a launch window. Corrections are credited.
Suggestions are welcome
Topic suggestions and corrections both go to the same place — email or the contact form. We read every suggestion, even the ones we end up not writing. External contributors who flag substantive corrections get credit in the update note.
Spotted an error or have a topic to suggest?
Email us directly or use the contact form. Every correction is reviewed and applied within a few business days, with credit if you'd like it.