A lot of developers “learn” System Design by watching one YouTube video on:
“How to Design Instagram”
Then they draw:
Load Balancer → App Servers → Redis → Kafka → DB
…and think they understand architecture.
You don’t understand System Design until you can explain:
Why Redis is needed
What happens when cache misses spike
Why Kafka instead of direct writes
How DB replication affects consistency
What fails first at 100x traffic
System Design is not diagram drawing.
It’s reasoning under constraints.
Shipped Codentis, a CLI-based AI agent with real-time streaming, persistent context, and 10+ developer commands. Designed it end-to-end with modular agent loops and async reliability. It’s already being used by devs. Also have experience at Samsung R&D working on ML pipelines. Would love to contribute.
Link: https://t.co/qvLzhCYY8J
I used to think Auth was simple.
“Login karo, token do, ho gaya.”
Then I tried building it properly:
– Secure password storage
– JWT lifecycle
– Middleware chaining
– Role-based access
– Handling edge cases
That’s when I realized:
> Authentication ≠ Authorization
> And most tutorials oversimplify it
So I wrote the guide I wish I had:
A practical breakdown with real backend flows (Node.js + JWT + MongoDB)
If you’re a developer, this will save you hours of confusion.
Read 👇
https://t.co/FQ2MJIFwyZ
You can also find this blog on blogs page in my portfolio website: https://t.co/tn0nFTv0sx
Just gave my portfolio a fresh update 🚀
Built, shipped, and refined projects I’m genuinely proud of especially in AI and full-stack systems.
Would love for you to check it out and share feedback: https://t.co/dBmLkOyza6
Always building. Always improving.