anyone currently in hyderabad?

How do you find a job, in 2026?

i begin my failure arc today.

Are we cooked? 🥲🫣

made this extremely cute pwa utility app. Can't wait to launch it. 🥹

My open-source System Design course is now live! github.com/karanpratapsingh/… #systemdesign #distributedsystems #softwarearchitecture

just realised i have been doing 16 hour shift 😔 No time for personal development.

how is there a sudden surge of hiring frontend devs?

If you're a senior engineer please leave an advice that can really be helpful for people who are looking for switch.

the job market is soo bad, idk how people are still getting hired.

How do you find freelance clients?

Concepts all devs should be aware of: - SOLID principles - Message queue(event driven) - Caching - Deployment - Linux - Design patterns - CAP theorem - Containerization - Load Balancing

what do you do when you get everything you ever wanted?

If I were an incoming (or younger) engineer breaking into tech today… my roadmap would look nothing like the one I followed. Because the game has changed. And the winners will be the ones who learn to play this version, not the 10 years old version. Here’s how I’d build myself from 0 → undeniable: 1) Master the boring fundamentals first Because this is the moat now. OS basics, data structures, networks, distributed systems, DB internals. AI can write code, but only you can reason about complexity, trade-offs, and failures. → This becomes your long-term leverage. 2) Treat AI like a power tool, not a brain I’d use LLMs to accelerate: But I’d force myself to explain back every line. If I can’t explain it, I don’t ship it. → This builds judgment. 3) Build 5–7 real projects that actually matter. Not tutorial toys. Projects where I have to debug concurrency, fight latency, design APIs, or deploy something that breaks at 03:00. → Pain is the fastest teacher in tech. 4) Specialize sooner, generalize always Pick 1 lane - backend, infra, ML systems, frontend performance and then go deep. But keep just enough breadth to talk architecture with anyone. → Depth builds value; breadth builds opportunity. 5) Learn to communicate like a senior engineer Write design docs. Think in trade-offs. Explain constraints. Ask better questions. → This alone moves careers 2–3 years faster. 6) Build proof of work that screams “I’m serious.” A portfolio. A GitHub with actual iteration. A devlog showing how you think. → Recruiters trust evidence more than adjectives. And the biggest thing I’d remind myself? You’re not competing with AI. You’re competing with people who use AI without understanding anything beneath it. Because fundamentals age slowly. But advantage compounds fast.