KISHAN DUBEY

Day 5 of Backend HTTP request structure, routing, middleware, and Postman connected a lot of dots today. The biggest takeaway? Node.js isn't just "JavaScript outside the browser"—it's the runtime that quietly powers the entire backend ecosystem.

Day 4 of Backend Realizing that HTTP defines the communication rules while TCP ensures reliable packet delivery completely changed my perspective. Also implemented a simple CRUD flow using HTTP methods to understand how URLs, routes, and requests work together.

Day 3 of Backend Once you understand why a concept exists, the next one becomes easier to understand. Today, package.json, node_modules, package-lock.json, and SemVer felt like pieces of the same puzzle.

Backend Day 2 A lot of confusion disappeared after understanding: • CommonJS vs ES Modules • require() vs import • module.exports vs export • Runtime responsibilities Small topics. Big clarity.

Backend finally started making sense today. DNS maps the domain. IP identifies the computer. Port identifies the running process. One small insight changed my perspective: Ports belong to running processes, not browser tabs. Learning one layer at a time.

Day 19 — Finished the last JavaScript lecture. Didn't expect sloppy mode vs strict mode and the behavior of this to be this interesting. Closures were another solid concept to learn. Now it's time to build projects. Next: Backend.

Day 18 of JavaScript Learned Callbacks, Promises, and async/await today. Callback hell was painful, Promises were better, but async/await feels much cleaner 🌅. Easier to read, debug, and maintain. Need more practice, but compared Callback Hell, Promises & Async/Await

Day 17 of JavaScript Finally understood what actually happens behind the scenes. Prototypes, Classes, Constructors, Inheritance and the Event Loop make way more sense now. One more piece of the JavaScript puzzle solved. 😌

Day 16 of JavaScript Finally learn about Memory Management in Javascript conceptually it is same in every JS engine but there is a chance of having subtle difference between there implementation.Stack/Heap is a mental model, not a JavaScript rule. Engine implementation varies.

Day 15 of JavaScript Learn not learn but got to know about APIs and trying to gain more info about it so that I can make more projects easily. And make two projects: weather webApp and GitHub profiles Viewer.Only two because seriously making UI is not as simple as I thought 🤔

Day 14 of JavaScript Done two projects both are games which required edge cases to solve and bugs which genuinely happen because of the assumption of programmers who think this logic will work and of course it didn't 😂. That's what I called bugs are 🌝. Demo vedio 👇🏿

Day 13 of JavaScript Completed this part of the day with making some projects just for practice and eventually I learned some important properties of CSS which was good along with JS fundamentals. You can see the code and the output in the demo vedio 👇🏿.

Day 12 of JavaScript In this part of the day I made some projects for practice which was genuinely helpful but it also helped in revising my concepts. But more projects are also left that should be completed within a time.

Created this project for a Hackathon competition. It's just give users system info, and environment variables info through a CLI where a user can choose options from the menu and even they can perform CRUD operation on files. A demo vedio show's everything about the project.

Day 10 of JavaScript Topic: CRUD operation and DOM manipulation Now this is what I wanted before starting this topic.This literally makes sense now. The thing I learnt: "Building projects can help you to understand things much easier than before" @rohit_negi9 and @CoderArmy.

Day 9 of JavaScript Today I learned that the browser doesn't work directly with HTML. It first parses the HTML and converts it into a DOM tree of objects, which is why JavaScript can interact with and modify web pages. @rohit_negi9 and @CoderArmy

Instead of only using built-in methods, I tried creating my own versions of: • forEach() • map() • filter() • reduce() @CoderArmy Rebuilding them helped me understand callbacks, prototypes, this, accumulators, and how these methods actually work behind the scenes.

Day 8 of JavaScript This part of the day covered several interesting topics and use cases. I can't fit everything into one post, so I wanted to share a few practice implementations that I built while learning. Sometimes the best way to learn a function is to build it yourself.

Left one is mine, right one is JavaScript's. Me: Builds forEk() and makes the array a parameter. JavaScript's forEach(): "You passed the whole array? Brother, I am the array." 💀 Turns out this was doing all the heavy lifting while I was fighting bugs for an hour. @CoderArmy

Day 7 of JavaScript @rohit_negi9 @CoderArmy Never thought a simple new Date() could lead me to learn about UTC, Unix Epoch, and how computers keep track of time. Also explored callbacks, IIFEs, and different function types today.