Hey devs. How's everyone doing?
Today's topic is a little heavy. But I'd rather be honest with you than write another post about frameworks and deployment pipelines.
Let's talk about something nobody really talks about — the silence.
The People Closest to You Don't Get It
You know that moment when you're genuinely excited about something you built, and you try to explain it to your younger sibling or a family member — and you watch their eyes glaze over in about four seconds?
They're not being mean. They just don't know what they're looking at.
And that's the painful part. The people who love you the most are often the ones least equipped to understand what you do. They don't know what it took. They don't know about the hours you spent debugging something that turned out to be a single missing semicolon. They don't know about the nights you told yourself "just this one last thing, then I'll sleep" — and then it was 3am and you were still there, forgetting to drink water, forgetting to eat, forgetting that the world outside your screen exists.
Only you know what went into it. Only you.
GitHub's Dirty Secret
Here's something nobody in the tutorials tells you.
You can pour months into a project, write clean code, deploy it properly, add a solid README, make the repo public — and it will sit there in complete silence. No stars. No forks. No issues. Nothing.
Public repos feel private. That's just the truth.
And it's not just GitHub. You share the link on LinkedIn — three likes, two of them are people who like everything. You post on Threads — silence. You try Reddit — your post gets three upvotes and a comment asking if it works on Windows. You spend time on Product Hunt, see what other people have shipped, and for a moment you feel like a beginner all over again even though you've been grinding for months.
I've been through all of this. I still go through it.
But Here's What Nobody Can Take From You
There's a feeling I want you to hold onto.
You know that moment when you're out somewhere — at a family dinner, at a gathering, just walking around — and you have this quiet knowledge in the back of your mind about what you've built? Nobody around you knows. Nobody's asking. But you know.
There's a kind of swag in that. A silent confidence. The thought that if the person standing in front of you knew what you'd actually built, they'd look at you differently.
That feeling is real. And it's yours. Nobody gave it to you — you earned it.
The Friend Who Never Compliments You
I want to tell you about my friend Meer Saad Marri.
Every time I build something and show him, he tears it apart. Every single time. He finds every flaw, questions every decision, and gives me exactly zero compliments. And honestly? In the moment, it drives me crazy. I can see my own work, I know what went into it, and here he is just... dismantling it.
But we have an unspoken rule between us: we never praise each other's work. Ever.
Because we both know what happens when you get too comfortable with compliments. You stop pushing. You start building for the applause instead of building for the product. And the day you start needing validation to keep going is the day your best work stops.
The hunger has to come from inside. Not from a notification.
The Day Is Coming
I genuinely believe this — and I'm not saying it to make you feel better. I'm saying it because I've seen it happen, slowly, in small ways.
One day, someone in your circle is going to come to you and say: "Bhai, have you seen this app? It's incredible. The developer must be something else."
And that app will be yours.
And you'll stay quiet. You'll just smile. And inside, there will be this deep, warm satisfaction that no amount of LinkedIn likes could ever give you.
That's the moment you're building toward. Every late night, every silent GitHub repo, every product that felt like it launched into a void — it's all going toward that moment.
Keep Going. For Yourself.
Don't build for applause. Don't build hoping someone will finally notice and validate what you already know about your own work.
Build because you can. Build because the problem exists and you're the one who sees it. Build because one day someone is going to use what you made and their life will be slightly easier, slightly better — and they won't even know your name.
That's enough. That has to be enough.
To every developer who shipped something today, yesterday, or six months ago that nobody has noticed yet — I see you. I salute you. Keep going.
Love you all. 🤝
Are your projects sitting live but feeling local? Drop a link in the comments. Let's actually look at each other's work.
Top comments (0)