---
title: "pushpesh kumar (@pushpeshkumar) | Hashnode"
description: "pushpesh kumar (@pushpeshkumar) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@pushpeshkumar"
---

@pushpeshkumar

# pushpesh kumar

@pushpeshkumar · Oslo, Norway · Joined April 2025

### [Demystifying JavaScript Promises: From Network Cables to fetch and Axios](https://pushpesh-js-articles.hashnode.dev/demystifying-javascript-promises-from-network-cables-to-fetch-and-axios?utm_source=hashnode&utm_medium=feed)

As a frontend developer, you will spend 95% of your time consuming promises rather than creating them. But when you are waiting for data from a backend service—like an API written in Java, Python, or

5 min read · [pushpesh-js-articles.hashnode.dev](https://pushpesh-js-articles.hashnode.dev/demystifying-javascript-promises-from-network-cables-to-fetch-and-axios?utm_source=hashnode&utm_medium=feed)

[Aug 5](https://hashnode.com/posts/demystifying-javascript-promises-from-network-cables-to-fetch-and-axios/6a72d7f2b502e7b9588f7c96)

### [JSON.parse() vs JSON.stringify()](https://pushpesh-js-articles.hashnode.dev/json-parse-vs-json-stringify?utm_source=hashnode&utm_medium=feed)

JSON.parse() and JSON.stringify() are complementary functions in JavaScript that convert data between JSON text and JavaScript objects. Think of them as opposite operations: JavaScript Object --string

3 min read · [pushpesh-js-articles.hashnode.dev](https://pushpesh-js-articles.hashnode.dev/json-parse-vs-json-stringify?utm_source=hashnode&utm_medium=feed)

[Jul 29](https://hashnode.com/posts/json-parse-vs-json-stringify/6a6996fa3d8fc0f74090e2d3)

### [React Context API](https://pushpesh-js-articles.hashnode.dev/react-context-api?utm_source=hashnode&utm_medium=feed)

🚀 What is Context API? The Context API is a built-in React feature that allows you to share data globally across components without passing props manually at every level. 👉 It solves the problem of

5 min read · [pushpesh-js-articles.hashnode.dev](https://pushpesh-js-articles.hashnode.dev/react-context-api?utm_source=hashnode&utm_medium=feed)

[Jun 9](https://hashnode.com/posts/react-context-api/6a27c7c08a4cee40436a427f)

### [Data flow advanced patterns](https://pushpesh-js-articles.hashnode.dev/data-flow-advanced-patterns?utm_source=hashnode&utm_medium=feed)

We’ll cover 3 important patterns: ✅ Controlled Components (Forms) ✅ Callback Pattern (Child → Parent communication) ✅ Context API (avoid prop drilling completely) ✅ 1. Controlled Components (For

4 min read · [pushpesh-js-articles.hashnode.dev](https://pushpesh-js-articles.hashnode.dev/data-flow-advanced-patterns?utm_source=hashnode&utm_medium=feed)

[Jun 9](https://hashnode.com/posts/data-flow-advanced-patterns/6a27c2574288fff78c1e01f8)

### [Data flow mental map in React](https://pushpesh-js-articles.hashnode.dev/data-flow-mental-map-in-react?utm_source=hashnode&utm_medium=feed)

🧠 1. The Core Decision Rule (Golden Rule) Whenever you're building something, ask: 👉 “Who owns this data?” That determines everything. ✅ 2. When to Send Data (Parent → Child) ✔ Use this when: Chil

5 min read · [pushpesh-js-articles.hashnode.dev](https://pushpesh-js-articles.hashnode.dev/data-flow-mental-map-in-react?utm_source=hashnode&utm_medium=feed)

[Jun 9](https://hashnode.com/posts/data-flow-mental-map-in-react/6a27be8c22b0301bcda70b90)