Hit a point today where writing more code wasn't the answer. refactoring was. JWT auth was living inside every controller separately. same logic. copy pasted. works until it doesn't. pulled it all into a single auth middleware. now it sits in front of every protected route, identifies the user, attaches them to the request, done. One place. one job. then built the follow model follower and followee both referencing the user. One simple schema that will eventually power the entire feed, follower counts, following lists. Everything that makes instagram feel like instagram starts here. Only problem today mongodb atlas blocked my ip. two minutes to whitelist it. back to building. @sheryians_ Cohort 2 @ankurdotio . #Backend #NodeJS #BuildingInPublic

I was so confident today. multer installed. logic clean. code looking good. then this showed up TypeError: Cannot read properties of undefined (reading 'buffer') Stared at it for way too long. Turns out i just forgot to attach multer to the route. express had no idea a file was in the request. just picked it up, shrugged and handed my controller absolutely nothing. one line of middleware. that's it. that's the whole fix. then imagekit decided to move things around in their docs. wrong method. wrong field in postman. every fix came with a free bonus problem attached. But when it finally worked a logged in user creating a post, uploading an image, stored on CDN, protected by JWT on an instagram clone i built myself that feeling makes every frustrating hour worth it. no tutorial teaches you this. bugs do. @sheryians_ Cohort 2 @ankurdotio . #Backend #NodeJS #BuildingInPublic

today i finally understood how instagram knows it's you. not your username. not your email. a cookie. when you log in, the server bakes your user ID into a JWT and stores it in a cookie. every request after that carries it automatically. backend reads it, verifies it, knows exactly who you are. writing the JWT extraction code was harder than expected. what happens when the token is missing? what happens when it's invalid? each case handled differently. a backend that doesn't verify who's making a request isn't a backend. it's an open door. building this into my instagram clone today. getting more real every day. @sheryians_ Cohort 2 @ankurdotio .

built the post creation feature for my instagram clone today. upload an image. store it on CDN. route protected by auth. end to end working. sounds simple. was not simple. multer, imagekit, bcrypt three tools, three docs, all needing to work together. also my first time ever reading official documentation in my life. nobody tells you how to read docs for the first time. you just open the page, try something, watch it break, go back and read more carefully. typos. postman not cooperating. debugging loops. but it works. and every bug fixed today is a bug i won't make twice. @sheryians_ Cohort 2 @ankurdotio .

exams. family wedding. two weeks of watching classes without being able to code. today i finally got my time back. first thing i did opened a blank folder and started catching up. building an instagram backend from scratch. express, mongoose, JWT, hashed passwords, auth routes done. been quiet for too long. starting today i'm going to be very active on here projects from class, projects of my own, the full journey not just the good parts. everyone falls behind sometimes. what matters is what you do the day you get your time back. today was that day. let's go. via @sheryians_ Cohort 2 with @ankurdotio.

you've been receiving web pages in your inbox your entire life. you just didn't know it. emails are written in HTML. every branded email with logos, buttons, and colors it's a web page rendered inside your mail client. learned this while building an OTP verification system from scratch yesterday. nodemailer, gmail SMTP, expiry logic, the whole thing. the best part of backend isn't the code. it's realizing how much is happening behind things you use every day without thinking. shoutout to @ankurdotio at @sheryians_ Cohort 2.

most people think they need to know everything before they start building. that's why they never start. you don't need to be ready. you need to be curious.

picked one of the most awarded design agency sites on the internet and rebuilt it from scratch. GSAP animations, locomotive scroll, morphing SVGs, video hover interactions, staggered nav reveals. the hard part wasn't the code. it was reverse engineering every micro-interaction without a single hint. that's the skill nobody talks about.

i went quiet for a few days. not because i stopped building because i was actually heads down learning things worth talking about. here's what i figured out while i was gone: most devs think about what their code does. very few think about what their code does when it breaks. silent data loss from file collisions. no error. no warning. just gone. that's what pushed me to properly learn ImageKit and Node's crypto module this week. CDN delivery, collision-resistant IDs, infrastructure that holds under real load. lazy person rule fix it right once so you never fix it again. what's one thing you've built that broke in a way you didn't expect? drop it below 👇 #Backend #BuildingInPublic #NodeJS

Nobody talks about this part of learning full stack: Everything works separately. Then you try to connect frontend backend and suddenly nothing works. That's where the real growth happens.