To start, I am a 2026 engineering graduate. I got placed through my college—maybe not at the elite company you might be looking to get into, but a decent one. Right now, I am waiting for my joining letter. I thought about how not to waste this precious time, and concluded I'd rather waste yours instead (relax, it’s a joke).
I am writing this to tell you to take a breath—you are going to figure it out. The industry makes you feel like if you don't know 15 frameworks by age 22, you're already behind. It's a lie. Whether you are deep in engineering, switching into tech, or doing something completely different, stop obsessing over the 10 things that you couldn't achieve. There are hundreds of paths you haven't even tried yet. No guru, perfect roadmap, or mentor is coming to write the code for you. The friction you feel right now—the rejections, the burnout, the confusion? That isn't the enemy. Just like adding weight to the bar, that friction is required to build you.
When you look online, the tech world is full of "perfect" developers. You see flawless desk setups, instant bug fixes, and "Ultimate 2026 Roadmaps." But you rarely see the messy middle. There is a lot of talk about the destination, but very little about the friction of the journey.
So, I am going to do the opposite. I’m not here to be a guru, and I don't have a magical formula for clearing interviews. I am here to build in public.
Instead of generic advice, I’ll be sharing the actual problems I hit—whether that’s untangling a brutal DSA pattern, debugging a broken project architecture, or managing the mental fatigue of the grind. I’ll share my roadblocks, the exact steps I take to fix them, and I want to hear about yours. Let's figure out what software engineering actually looks like when you strip away the filters.
Why should you read my blogs?
To break the tutorial loop: If you are tired of passively copying code without understanding the "why" behind it, we are going to fix that.
To see the raw architecture: I will be breaking down how backend systems and algorithms actually work using clear, real-world models. No gatekeeping, no unnecessary jargon.
To build the discipline: Software engineering isn't just about syntax; it is about the mental endurance to debug, optimize, and push through friction. We will cover the habits that keep the human system running.
To step into the arena: If you want to stop watching others build, see what an engineer actually experiences in the trenches, and maybe even build something together—this is your starting line.
Top comments (0)