---
title: "kunal goel (@frontend-guide) | Hashnode"
description: "Full Stack Developer with 3+ years of experience building scalable SaaS web applications using the MERN stack (MongoDB, Express.js, React.js, Node.js). Skill..."
url: "https://hashnode.com/@frontend-guide"
---

@frontend-guide

# kunal goel

@frontend-guide · Jaipur · Joined March 2026

### [Deep Dive into React Fiber: How React Actually Reconciles Your UI](https://blog.kunalgoel.dev/deep-dive-into-react-fiber-how-react-actually-reconciles-your-ui?utm_source=hashnode&utm_medium=feed)

Frontend System Design Series — From virtual DOM diffing to commit mutations — a complete walkthrough of every phase and step React takes before a single pixel changes on screen. Why This Topic Matt

8 min read · [blog.kunalgoel.dev](https://blog.kunalgoel.dev/deep-dive-into-react-fiber-how-react-actually-reconciles-your-ui?utm_source=hashnode&utm_medium=feed)

[May 30](https://hashnode.com/posts/deep-dive-into-react-fiber-how-react-actually-reconciles-your-ui/6a1b3fae860ed1708197720d)

### [Designing YouTube's Frontend System — Streams, Feeds, and Scale](https://blog.kunalgoel.dev/designing-youtube-s-frontend-system-streams-feeds-and-scale?utm_source=hashnode&utm_medium=feed)

Frontend System Design Series — In this series, I break down how the world's most complex frontend systems are architected. 🎬 The Scale Problem YouTube serves 500 hours of video every minute. Over

10 min read · [blog.kunalgoel.dev](https://blog.kunalgoel.dev/designing-youtube-s-frontend-system-streams-feeds-and-scale?utm_source=hashnode&utm_medium=feed)

[May 22](https://hashnode.com/posts/designing-youtube-s-frontend-system-streams-feeds-and-scale/6a105bb81f237623eafb4cb6)

### [State Management Isn't a Preference. It's Architecture.](https://blog.kunalgoel.dev/state-management-isn-t-a-preference-it-s-architecture?utm_source=hashnode&utm_medium=feed)

Day 5 — Frontend System Design Series · 8 min read Why "it depends" is the wrong answer — and how to reason about state in a system design interview like you've built things that broke. Here's wha

8 min read · [blog.kunalgoel.dev](https://blog.kunalgoel.dev/state-management-isn-t-a-preference-it-s-architecture?utm_source=hashnode&utm_medium=feed)

[May 15](https://hashnode.com/posts/state-management-isn-t-a-preference-it-s-architecture/6a06b89b9c794cb653f046d1)

### [Performance Patterns That Actually Matter in Production](https://blog.kunalgoel.dev/performance-patterns-that-actually-matter-in-production?utm_source=hashnode&utm_medium=feed)

We're talking performance today. And before you scroll away thinking "yeah yeah, lazy load your images, use a CDN" — I promise this is not that blog. We're going deeper. We're talking about the stuff

8 min read · [blog.kunalgoel.dev](https://blog.kunalgoel.dev/performance-patterns-that-actually-matter-in-production?utm_source=hashnode&utm_medium=feed)

[May 12](https://hashnode.com/posts/performance-patterns-that-actually-matter-in-production/6a03488f937b84f7799991fb)

### [Component Design Patterns Every React Dev Should Know (Compound Components, Render Props & Custom Hooks)](https://blog.kunalgoel.dev/component-design-patterns-every-react-dev-should-know-compound-components-render-props-custom-hooks?utm_source=hashnode&utm_medium=feed)

First, a decision diagram — the question you should ask before picking a pattern: I used to build components in one big blob. Everything in one file — state, logic, markup, API calls. It worked. Unt

6 min read · [blog.kunalgoel.dev](https://blog.kunalgoel.dev/component-design-patterns-every-react-dev-should-know-compound-components-render-props-custom-hooks?utm_source=hashnode&utm_medium=feed)

[Mar 26](https://hashnode.com/posts/component-design-patterns-every-react-dev-should-know-compound-components-render-props-custom-hooks/69c4f40310e664c5da87b150)