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

@devcode900

# Anand

@devcode900 · Joined January 2026

### [Express Middleware: The Checkpoints Between Request and Response](https://middleware-express-working-any.hashnode.dev/express-middleware-the-checkpoints-between-request-and-response?utm_source=hashnode&utm_medium=feed)

Imagine you are checking into a hotel. You do not walk straight from the street into your room. You pass through a series of checkpoints: the doorman opens the door, the receptionist verifies your res

6 min read · [middleware-express-working-any.hashnode.dev](https://middleware-express-working-any.hashnode.dev/express-middleware-the-checkpoints-between-request-and-response?utm_source=hashnode&utm_medium=feed)

[May 10](https://hashnode.com/posts/express-middleware-the-checkpoints-between-request-and-response/6a00bbcee3eebc2e20a91afe)

### [URL Parameters vs. Query Parameters: Finding Your Way Around the Web](https://url-parameter-vs-query-string-express-any.hashnode.dev/url-parameters-vs-query-parameters-finding-your-way-around-the-web?utm_source=hashnode&utm_medium=feed)

Imagine you walk into a massive library. Some books are organized by a unique call number stamped on their spine — a precise identifier that points to exactly one book, like QA76.5.B57 1999. Other tim

5 min read · [url-parameter-vs-query-string-express-any.hashnode.dev](https://url-parameter-vs-query-string-express-any.hashnode.dev/url-parameters-vs-query-parameters-finding-your-way-around-the-web?utm_source=hashnode&utm_medium=feed)

[May 10](https://hashnode.com/posts/url-parameters-vs-query-parameters-finding-your-way-around-the-web/6a00bb38e3eebc2e20a88696)

### [Where Do Uploaded Files Go? Storing and Serving Files in Node.js](https://uploaded-file-an-serving-them-in-express-any.hashnode.dev/where-do-uploaded-files-go-storing-and-serving-files-in-node-js?utm_source=hashnode&utm_medium=feed)

Imagine you run a photography studio. When clients hand you their digital photos, you do not just scatter them on the front desk. You organize them into folders — perhaps by date or by client name — s

6 min read · [uploaded-file-an-serving-them-in-express-any.hashnode.dev](https://uploaded-file-an-serving-them-in-express-any.hashnode.dev/where-do-uploaded-files-go-storing-and-serving-files-in-node-js?utm_source=hashnode&utm_medium=feed)

[May 10](https://hashnode.com/posts/where-do-uploaded-files-go-storing-and-serving-files-in-node-js/6a00baabe3eebc2e20a80f2c)

### [Handling File Uploads in Node.js: Why You Need Multer and How It Works](https://file-upload-using-express-with-multer-js.hashnode.dev/handling-file-uploads-in-node-js-why-you-need-multer-and-how-it-works?utm_source=hashnode&utm_medium=feed)

Imagine you are moving into a new apartment. You could try to carry your entire sofa, bookshelf, and refrigerator through the front door all at once, squeezed into a single box. It would not fit. It w

6 min read · [file-upload-using-express-with-multer-js.hashnode.dev](https://file-upload-using-express-with-multer-js.hashnode.dev/handling-file-uploads-in-node-js-why-you-need-multer-and-how-it-works?utm_source=hashnode&utm_medium=feed)

[May 10](https://hashnode.com/posts/handling-file-uploads-in-node-js-why-you-need-multer-and-how-it-works/6a00ba25e3eebc2e20a7a63c)

### [REST APIs: The Language of the Web](https://rest-api-design-using-express-any.hashnode.dev/rest-apis-the-language-of-the-web?utm_source=hashnode&utm_medium=feed)

Imagine you walk into a library. You do not barge into the storage room and rummage through boxes. Instead, you interact with the system through a clear, predictable interface. You ask the librarian f

6 min read · [rest-api-design-using-express-any.hashnode.dev](https://rest-api-design-using-express-any.hashnode.dev/rest-apis-the-language-of-the-web?utm_source=hashnode&utm_medium=feed)

[May 10](https://hashnode.com/posts/rest-apis-the-language-of-the-web/6a00b996e3eebc2e20a734bc)