Thoughts on books I read, things I learn, and ideas worth sharing with the world.
Most developers skip the design phase entirely — or worse, let AI decide everything. Here's the workflow I use to go from a vague idea to a shipped site that looks intentional, not generated.
I researched countries, job markets, and interview cultures — and realized the best path isn't chasing offers. It's becoming the kind of engineer great teams want to work with.
Everything I learned about contributing to the Linux kernel — from picking your first issue to getting merged into mainline. No fluff, no gatekeeping, just the real game.
Everything you need to know about accepting payments in India — how it works, which gateway to use, when you get paid, and how to implement it in Next.js.
We spend 4 years in college, crack exams, collect certificates, and chase jobs. But somewhere along the way, we forgot what engineering actually means. This is my honest rant — and my own question back to myself.
I spent a day chasing one annoying problem: every site an AI builds for me looks generic — purple gradient, no images, dead vibe. Here's the stack that actually fixed it, and the one site to open before every design session.
What if focusing on just one thing could change everything? Gary Keller's 'The ONE Thing' taught me that extraordinary results come from narrowing your focus — not widening it.