Rakesh K @codersGyan

@adityahvyas There is a next step to verify further 😅

Years ago at a bank, they sat us all down for a cyber security training. I remember thinking, when am I ever going to use any of this. Now when one of these emails lands in my inbox, within seconds I catch it. And just today one did. A "paid partnership" for a YouTube campaign. One look and I knew it was fake. So here's the thing. Learnings never go waste. Sometimes they just sit quietly for a few years and wait for the right moment. Keep learning, even the stuff that feels useless right now.

Have you noticed almost every product you open now has AI quietly baked in? YouTube Studio just did it too. Gemini sits right inside it. You hand it a video, it gives you back a thumbnail. I tried it on my Go Panic and Recover video. Not great. But better than me doing it manually, and that's kind of the point. These tools don't have to be amazing yet. They just have to beat the version where you're stuck doing the whole thing alone.

Why can a Go project have more than one main package? Simple. Each main package's main function produces its own executable. So your api, web, worker, and cli can all live in one repo, each sitting in its own folder under cmd, each building its own binary. One go.mod, many entry points. Very handy once your app grows past a single service.

I've seen so many developers start a project with dozens of folders on day zero. Don't. You don't need that structure yet. Bring in a folder or a file only when it earns its place. If it hasn't earned it, then naa, I'm not creating it. Less to maintain, and you move faster. The project I'm building right now follows exactly this, and it's going up on YouTube soon. Stay tuned.

youtu.be/tNPY7tki1HQ?si…

Funny thing about the world we live in. The moment something is free, people quietly assume it's worth less. I'll say this plainly. Everything I covered in my videos, you will not find in any premium course. And it's not just this one. Every single video on my channel is a premium piece that happens to cost nothing. Because for me, free and paid are the same. Same effort, same energy, both times. Honestly I don't know how to do it any other way. Link's in the comments if you want to learn Go's most powerful feature 😊

keyboard_arrow_left Previous keyboard_arrow_right Next

@adityahvyas Here also manually. It’s just a convention.

In Go you keep seeing functions named MustSomething. MustLoad, MustCompile, MustParse. So what's the deal with that Must? It's a convention. Normally in Go an error is a value, so you return it and let the caller decide what to do. But some things just have to work, or your program has no business running. Your config is one of them. If it can't load at startup, what are you going to do, run with no config? So MustLoad doesn't return an error. It panics inside if it fails. No err to check, nothing to handle. It either hands you a valid config or it stops the program right there. Use this for the things that must happen at startup. Panic early, fail loud, no need to recover.

@adityahvyas 😅 maan pe le liya

Checked the leaderboard today, and these are the folks responsible for my DRM bill spiking last month 😅 Jokes apart, I've genuinely never seen dedication like this. People sitting down day after day, grinding through backend and GenAI, stacking up XP because they actually want to get good at this. Not for a certificate. For the skill. To everyone putting in the hours, you all are doing great work. Keep it up.

Every time I write login, I do one small thing on line 122 that looks completely pointless. If the email isn't in the database, I still run a bcrypt compare against a dummy hash before I return. Why would you hash a password for a user that doesn't exist? Because of timing. If you return early the moment the user is missing, that path is fast. The path where the user does exist is slow, because bcrypt is slow on purpose. An attacker times your responses and now knows which emails are registered. That's user enumeration. So I make both paths cost about the same. User exists or not, the response comes back in roughly the same time. Nothing leaks. Small detail, big difference. Detailed video on this coming soon, stay tuned.

codersgyan.substack.com

541 of you are reading my newsletter now. 156 joined in the last 30 days, and honestly that still surprises me. Here's what I've noticed. Many of you don't love reading, you love watching. I get it. But reading gives you something video can't, and that's slowness. You process it bit by bit, at your own pace. And depth comes from slowness. This is where I share backend engineering insights, my own experiments, all the backend heavy stuff I'm working through. If you've been meaning to go deeper, give it a try. Link in the comments.

youtube.com/watch?v=nJoFk4…

I keep sending this one video to anyone trying to finally understand Go channels. Channels are the most important feature Go has, and they're also the one people get stuck on the most. In this I built a Mailchimp-style email service end to end, producer and consumer, and we went deep into how the whole thing works under the hood. If channels have been confusing you for a while, give this a watch.

everything's going to live here: codersgyan.com

So this is the thing we've been building quietly. One place where you land, pick your course, and start the work that actually moves your career. That's it. No maze, no twenty tabs. You come here, you choose, you begin. We're launching it soon. Honestly a little nervous to show it, but this is where the journey starts now.

📚 Day 7 of Building a Microservices-Based Project After spending the past few days working on backend services, I recently started building the Admin Panel frontend and exploring how authentication flows are implemented on the client side. Some of the things I explored: 🔹 Setting up a React + Vite + TypeScript project 🔹 Configuring routing with React Router 🔹 Setting up component testing with Vitest and React Testing Library 🔹 Building the login experience using Ant Design 🔹 Integrating authentication APIs using React Query 🔹 Managing authentication state with Zustand 🔹 Implementing protected routes for authenticated users 🔹 Persisting authentication state across page refreshes 🔹 Exploring automatic token refresh using Axios interceptors One thing that stood out to me was how much coordination is required between the frontend and backend to provide a seamless authentication experience. Features like protected routes, session persistence, and silent token refresh all work together behind the scenes to create a better user experience. I'm still learning a lot about frontend architecture and authentication patterns, but working on the Admin UI has helped me better understand how these pieces fit together in real-world applications. @codersGyan #React #TypeScript #Vite #ReactQuery #Zustand #Authentication #FrontendDevelopment #Microservices #SoftwareEngineering #LearningInPublic

keyboard_arrow_left Previous keyboard_arrow_right Next

The /internal folder in Go is the most misunderstood thing in the whole project layout. Most people use it once at the top level, just to hide code from the outside world. But here's what very few know. You can nest an internal folder inside another internal folder. And that's the real trick. Each one draws a boundary, so one package can't reach into another package's guts. That's how you build a proper modular monolith, not just a folder full of packages pretending to be modules.