If you’re a founder or work in a startup, you should know- no one cares about you. Not your employees. Not your investors. Not your customers. Not your insurance. Not your team members. Nobody. Everyone will pretend because they want something from you. But if you stop caring about yourself, you’re screwed. Your priority should be to work on your health- both physical and mental. Just the way you work on your startup. Else there will be no coming back. The number of people who have earned so much and are leaving it all to fix what’s broken is mind boggling. Your ability to bounce back when things don’t work is a bigger status symbol than your valuation or esops. You are the greatest project you’ll ever work on.
i especially hate CVs. what the fuck am i supposed to learn there? it's literally negative information
bunch of high level abstract sentences. "leading a project" or "making something 40% more efficient" means nothing
send deep insights that no one else could have or something
been using AI to write code for almost a year now and i still keep seeing the same issues, even with frontier models like Fable5, Opus 4.8 and GPT-5.5
1) if "A" dependency already does it, AI installs "B" anyway.
2) 30 lines of logic somehow turns into a 200 line function.
3) a simple if else becomes 50 lines of abstractions which isnt needed anyways.
worked with quite a few teammates too and whenever i asked "why was this change even needed?" or "why this PR?", there was almost always silence
way too many people are relying on AI without thinking about the most important part of coding: knowing what not to write.
One of my favs:
"Monk and the empty boat.
A monk decides to meditate alone, away from his monastery. He takes his boat out to the middle of the lake, moors it there, closes his eyes and begins his meditation.
After a few hours of undisturbed silence, he suddenly feels the bump of another boat colliding with his own. With his eyes still closed, he senses his anger rising, and by the time he opens his eyes, he is ready to scream at the boatman who dared disturb his meditation.
But when he opens his eyes, he sees it is an empty boat that had probably got untethered and floated to the middle of the lake.
At that moment, the monk achieves self-realization, and understands that the anger is within him;
it merely needs the bump of an external object to provoke it out of him. From then on, whenever he came across someone who irritated him or provoked him to anger, he reminded himself :
'The other person is merely an empty boat. The anger is within me'
In reality, we all have the anger within us, all the time, All it needs is someone, like the empty boat, to provoke it."
if you are a curious engineer, it is so difficult not to have fomo.
every other domain seems interesting
every other book seems worth reading
every other problem seems worth solving
every other project looks like the next big thing
every other framework feels like something you should learn.
literally every single thing is a distraction. imo, there is no way to even deal with that.
One of the best pieces of life/career advice I’ve ever received:
Do not do X in order to do Y. Just do Y.
You get ready for something by just doing the thing
Deep Dive on the State of RWAs on @Solana
From BlackRock and Franklin Templeton to tokenized SpaceX shares that crossed $350M in trading volume within 24 hours...
A deep dive into what's actually happening, why it matters, and where the biggest opportunities for builders lie.
⏱️ Timestamps:
00:00 → Why RWAs are getting so much attention
00:25 → What are RWAs?
00:50 → Why they matter
01:29 → The numbers behind the momentum
02:14 → Why institutions are choosing Solana
02:38 → The opportunity for builders
03:06 → Larry Fink's vision
Growing an agency isn't about one big move. It's about building systems, improving processes, talking to customers, and showing up every day.
Here's a behind-the-scenes look at what went into today's work as we expand into the US market. Looking forward to sharing more lessons from the journey.
09 July 2026: Session 1 ( ~4.5 hrs )
> Worked on context graph layer of incident agent
> Read about benchmarking in go
> Read 2-3 more random blogs from my reading list which turned out to be AI slop, people be writing anything nowadays (crying emoji)
Every backend engineer should know how distributed systems work and their basics.
If you want to actually master Distributed Systems, stop hoarding tutorials and watch Martin Kleppmann’s free lecture series.
It completely changes how you think about building scalable, fault-tolerant backends.
Link in the replies. 👇
It is a damn privilege to be working on technology that demands mastery of the fundamental concepts of physics, mathematics, mechanisms, software, and electronics - all at once from you.
It's like every day I come in and get to attack these fundamentals again, learn and re-learning them from the ground-up, and then get to use them to solve problems.
What makes things even better is that I get to write content, manage operations, get myself involved in business and learn far and beyond the role that I am designated with. I know this sounds like promo, but it's literally my thoughts after a month and 2 days at this org that I am penning down at 8:59 AM on a random Friday.
The shortcomings within me are shining brighter and I cannot sweep em under the rug anymore, the strengths within me are being hammered upon so that I can generate value for me and the company at the same time -
ayy man, you'll come across a job at a deeptech startup in your 20s. It is very, very important for you to take accept it and get to work.
09 July 2026: Session 1 ( ~4.5 hrs )
> Worked on context graph layer of incident agent
> Read about benchmarking in go
> Read 2-3 more random blogs from my reading list which turned out to be AI slop, people be writing anything nowadays (crying emoji)
07/07/26: ~11 hrs
> Played around with UTM for the first time ( mac experience was bad, it was very slow even with 8g shared ram and 4 cores, will try Linux next )
> Completed the web crawler project
> Built a whatsapp scraping bot
> Forgot to shower obv
> Updated resume
> Implemented a fifo queue in JS lol
> Read some open source evals
> Created golden datasets for incident agent
> and a few more things then my brain crashed
the real reason you’re tired all the time: it’s not your workload. it’s your open loops. the text you haven’t answered. the apology you owe. the decision you’re avoiding. the conversation you keep postponing. these run in the background of your mind all day, draining your battery. close your loops. watch your energy return. mental clutter is more exhausting than physical work ever will be.
imagine being OpenAI, one of the biggest AI companies in the world, and still shipping docs that don't match the actual Codex CLI
how am i supposed to install this?
07/07/26: ~11 hrs
> Played around with UTM for the first time ( mac experience was bad, it was very slow even with 8g shared ram and 4 cores, will try Linux next )
> Completed the web crawler project
> Built a whatsapp scraping bot
> Forgot to shower obv
> Updated resume
> Implemented a fifo queue in JS lol
> Read some open source evals
> Created golden datasets for incident agent
> and a few more things then my brain crashed
06 July 2026: Session 1 (~6hrs)
Next few weeks are booked for Go coz it’s been so long
> speed ran go docs
> built a concurrent web crawler ( from first principles hehe)
> ate very tasty sandwiches made by my lovely Bihari flatmate
> read about gollvm, gc and gccgo ( diff go compilers, their working and implementations )
I’ll also try to do some OSS contributions, maybe in k8s idk. Please do recommend any new, interesting and activity maintained projects if you know