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

@prafulchaudhari

# Prafull Chaudhari

@prafulchaudhari · Surat, India · Joined August 2025

### [Storing Uploaded Files and Serving Them in Express](https://web-dev-articles.hashnode.dev/storing-uploaded-files-and-serving-them-in-express?utm_source=hashnode&utm_medium=feed)

Accepting a file upload is just the first step. Knowing where to put it, how to name it safely, and how to serve it back, that's what makes it production-ready. The Two-Part Problem When a user uplo

12 min read · [web-dev-articles.hashnode.dev](https://web-dev-articles.hashnode.dev/storing-uploaded-files-and-serving-them-in-express?utm_source=hashnode&utm_medium=feed)

[Apr 23](https://hashnode.com/posts/storing-uploaded-files-and-serving-them-in-express/69e9b60c0ae1824cf52610b2)

### [Sessions vs JWT vs Cookies: Understanding Authentication Approaches](https://web-dev-articles.hashnode.dev/sessions-vs-jwt-vs-cookies-understanding-authentication-approaches?utm_source=hashnode&utm_medium=feed)

Every web app needs to remember who you are. How it does that, sessions, cookies, or tokens, shapes the entire architecture. The Core Problem: HTTP Is Forgetful HTTP is stateless. Every request your

13 min read · [web-dev-articles.hashnode.dev](https://web-dev-articles.hashnode.dev/sessions-vs-jwt-vs-cookies-understanding-authentication-approaches?utm_source=hashnode&utm_medium=feed)

[Apr 23](https://hashnode.com/posts/sessions-vs-jwt-vs-cookies-understanding-authentication-approaches/69e9b1558991b5ba1596523a)

### [Dispatches from Below the Shell](https://web-dev-articles.hashnode.dev/dispatches-from-below-the-shell?utm_source=hashnode&utm_medium=feed)

What happens when you stop running commands and start reading the filesystem like a system detective. Finding 01 — DNS is a three-layer negotiation, not a single config file Networking | /etc/resolv.

9 min read · [web-dev-articles.hashnode.dev](https://web-dev-articles.hashnode.dev/dispatches-from-below-the-shell?utm_source=hashnode&utm_medium=feed)

[Apr 22](https://hashnode.com/posts/dispatches-from-below-the-shell/69e8ddc35d1c1071056005cd)

### [Async Code in Node.js: Callbacks and Promises](https://web-dev-articles.hashnode.dev/async-code-in-node-js-callbacks-and-promises?utm_source=hashnode&utm_medium=feed)

Node.js is built to never wait. Understanding how it handles async work is the key to writing good server-side JavaScript. Why Async Code Exists in Node.js Node.js runs on a single thread. That mean

11 min read · [web-dev-articles.hashnode.dev](https://web-dev-articles.hashnode.dev/async-code-in-node-js-callbacks-and-promises?utm_source=hashnode&utm_medium=feed)

[Apr 21](https://hashnode.com/posts/async-code-in-node-js-callbacks-and-promises/69e6fd4ec9501dd01073cc4e)

### [Understanding the this Keyword in JavaScript](https://web-dev-articles.hashnode.dev/understanding-the-this-keyword-in-javascript?utm_source=hashnode&utm_medium=feed)

this doesn't mean "this function" or "this file". It means "whoever called me". That one shift in thinking makes everything click. Why this Confuses People this is one of those things that seems sim

10 min read · [web-dev-articles.hashnode.dev](https://web-dev-articles.hashnode.dev/understanding-the-this-keyword-in-javascript?utm_source=hashnode&utm_medium=feed)

[Apr 21](https://hashnode.com/posts/understanding-the-this-keyword-in-javascript/69e6f9f8c9501dd0107182d6)