It wasn’t an ideological safe seat for the BJP . It was a family fiefdom of the Sinha’s. #Bankipur saw a clash between two personalities. It was a giant @PrashantKishor vs an unknown pigmy some Sinha. And a non performing Chief minister made it easier for JSP to walk away with a trophy. No big lessons emerge from this non battle.
Brought to you by the creators of USD₮, tether.wallet is designed for everyday transactionsBrought to you by the creators of USD₮, tether.wallet is designed for everyday transactions.
Sanju Samson once held the record for most consecutive matches missed before getting another T20I chance for India.
Imagine the self-doubt. The waiting. The silence.
Yet he kept showing up, performing in IPL, believing he still belonged.
Sometimes your turn comes late - but it comes to those who don’t quit. 💙🇮🇳
Prashant Kishor’s defeat feels personal for everyone who believed that politics could still be won through grit and hard work.
His loss isn’t just his - it’s a setback for those who hoped merit could still challenge the system.
Was especially curious to ask @karpathy why self-driving cars took a decade+ from stellar demo rides to even somewhat deployed. Andrej led AI at Tesla for 5 years.
I really wanted to know whether these frictions should lengthen our AGI timelines, or whether they were idiosyncratic to self driving.
Driving has a really high cost of failure. Humans are surprisingly reliable drivers - we have a serious accident every 400,000 miles/7 years. And self-driving cars need to match or beat this safety profile before they can be deployed.
But are most domains like this? Before the interview, it seemed to me that almost every domain we would want to plug AGI into has a much lower cost of failure. If fully autonomous software engineers weren’t allowed to make a mistake for 7 years, deployment would indeed be super slow.
Andrej made an interesting point that I hadn’t heard before: compared to self driving, software engineering has a higher (and potentially unbounded) cost of failure:
> If you’re writing actual production-grade code, any kind of mistake could lead to a security vulnerability. Hundreds of millions of people’s personal Social Security numbers could get leaked.
> In self-driving, if things go wrong, you might get injured. There are worse outcomes. But in software, it’s almost unbounded how terrible something could be.
> In some ways, software engineering is a much harder problem [than self driving]. Self-driving is just one of thousands of things that people do. It’s almost like a single vertical. Whereas when we’re talking about general software engineering, there’s more surface area.
There’s potentially another reason why the LLM -> widely deployed AGI transition might happen much faster: LLMs give us perception, representations, and common sense (to deal with out of distribution examples) for free, whereas these had to be molded from scratch for self-driving cars. I asked Andrej about this:
> I don’t know how much we’re getting for free. LLMs are still pretty fallible and they have a lot of gaps that still need to be filled in. I don’t think that we’re getting magical generalization completely out of the box.
> The other aspect that I wanted to return to is that self-driving cars are nowhere near done still. The deployments are pretty minimal. Even Waymo has very few cars. They’ve built something that lives in the future. They’ve had to pull back the future, but they had to make it uneconomical.
> Also, when you look at these cars and there’s no one driving, there’s more human-in-the-loop than you might expect. In some sense, we haven’t actually removed the person, we’ve moved them to somewhere where you can’t see them.
watching one house being built - every detail matters.
they stress over every tile, every edge.
that’s the mindset to bring to work if i want to take ownership of my work.
Imagine if every business on X used AI like @Grok—answering queries in a human way using their own data. That could unlock a whole new revenue stream for X.