Rohit Nair

Caught between his love for sports, politics, economics and tech, nothing excites Rohit more than a discussion about travel plans! #humanWiki

[Aravind Srinivas @AravSrinivas]

Perplexity started as a small business tool for ourselves. We had 4 people and no revenue with AI at our fingertips.

The pivot to Computer is actually a full circle. Founders are using it to grow companies that matter to the economy and their communities. 

It’s rewarding to see it now powering small businesses and startups in big ways.

Perplexity is still a startup. We just 5X’ed revenue from $100M to $500M with only 34% growth in team size. 2x revenue growth in 2026 with same small team. And we’re just warming up.

Everyone here works at a small business, and everything we build is for people who build.

[Peter Walker @PeterJ_Walker]

A universal truth: most radar charts should just be bar charts.

Love your stuff, Anthropic!

[Joe Weisenthal @TheStalwart]

The fact that one can get an LLM to put together a cogent-sounding argument in favor of virtually any position has left me feeling cynical about human debate and discourse. That it’s (almost) all a game wholly sealed inside language itself without tether to the world.

[Andrej Karpathy @karpathy]

It is hard to communicate how much programming has changed due to AI in the last 2 months: not gradually and over time in the "progress as usual" way, but specifically this last December. There are a number of asterisks but imo coding agents basically didn’t work before December and basically work since - the models have significantly higher quality, long-term coherence and tenacity and they can power through large and long tasks, well past enough that it is extremely disruptive to the default programming workflow.

Just to give an example, over the weekend I was building a local video analysis dashboard for the cameras of my home so I wrote: “Here is the local IP and username/password of my DGX Spark. Log in, set up ssh keys, set up vLLM, download and bench Qwen3-VL, set up a server endpoint to inference videos, a basic web ui dashboard, test everything, set it up with systemd, record memory notes for yourself and write up a markdown report for me”. The agent went off for ~30 minutes, ran into multiple issues, researched solutions online, resolved them one by one, wrote the code, tested it, debugged it, set up the services, and came back with the report and it was just done. I didn’t touch anything. All of this could easily have been a weekend project just 3 months ago but today it’s something you kick off and forget about for 30 minutes.

As a result, programming is becoming unrecognizable. You’re not typing computer code into an editor like the way things were since computers were invented, that era is over. You're spinning up AI agents, giving them tasks *in English* and managing and reviewing their work in parallel. The biggest prize is in figuring out how you can keep ascending the layers of abstraction to set up long-running orchestrator Claws with all of the right tools, memory and instructions that productively manage multiple parallel Code instances for you. The leverage achievable via top tier "agentic engineering" feels very high right now.

It’s not perfect, it needs high-level direction, judgement, taste, oversight, iteration and hints and ideas. It works a lot better in some scenarios than others (e.g. especially for tasks that are well-specified and where you can verify/test functionality). The key is to build intuition to decompose the task just right to hand off the parts that work and help out around the edges. But imo, this is nowhere near "business as usual" time in software.

[Andrej Karpathy @karpathy]

A few random notes from claude coding quite a bit last few weeks.

Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words. It hurts the ego a bit but the power to operate over software in large "code actions" is just too net useful, especially once you adapt to it, configure it, learn to use it, and wrap your head around what it can and cannot do. This is easily the biggest change to my basic coding workflow in ~2 decades of programming and it happened over the course of a few weeks. I'd expect something similar to be happening to well into double digit percent of engineers out there, while the awareness of it in the general population feels well into low single digit percent.

IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side. The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly sloppy, hasty junior dev might do. The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking. They also don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs, they don't push back when they should, and they are still a little too sycophantic. Things get better in plan mode, but there is some need for a lightweight inline plan mode. They also really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves, etc. They will implement an inefficient, bloated, brittle construction over 1000 lines of code and it's up to you to be like "umm couldn't you just do this instead?" and they will be like "of course!" and immediately cut it down to 100 lines. They still sometimes change/remove comments and code they don't like or don't sufficiently understand as side effects, even if it is orthogonal to the task at hand. All of this happens despite a few simple attempts to fix it via instructions in CLAUDE . md. Despite all these issues, it is still a net huge improvement and it's very difficult to imagine going back to manual coding. TLDR everyone has their developing flow, my current is a small few CC sessions on the left in ghostty windows/tabs and an IDE on the right for viewing the code + manual edits.

Tenacity. It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. You realize that stamina is a core bottleneck to work and that with LLMs in hand it has been dramatically increased.

Speedups. It's not clear how to measure the "speedup" of LLM assistance. Certainly I feel net way faster at what I was going to do, but the main effect is that I do a lot more than I was going to do because 1) I can code up all kinds of things that just wouldn't have been worth coding before and 2) I can approach code that I couldn't work on before because of knowledge/skill issue. So certainly it's speedup, but it's possibly a lot more an expansion.

Leverage. LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go. Get it to write tests first and then pass them. Put it in the loop with a browser MCP. Write the naive algorithm that is very likely correct first, then ask it to optimize it while preserving correctness. Change your approach from imperative to declarative to get the agents looping longer and gain leverage.

Fun. I didn't anticipate that with agents programming feels *more* fun because a lot of the fill in the blanks drudgery is removed and what remains is the creative part. I also feel less blocked/stuck (which is not fun) and I experience a lot more courage because there's almost always a way to work hand in hand with it to make some positive progress. I have seen the opposite sentiment from other people too; LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building.

Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually. Generation (writing code) and discrimination (reading code) are different capabilities in the brain. Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it.

Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. We're also going to see a lot more AI hype productivity theater (is that even possible?), on the side of actual, real improvements.

Questions. A few of the questions on my mind:
- What happens to the "10X engineer" - the ratio of productivity between the mean and the max engineer? It's quite possible that this grows *a lot*.
- Armed with LLMs, do generalists increasingly outperform specialists? LLMs are a lot better at fill in the blanks (the micro) than grand strategy (the macro).
- What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music?
- How much of society is bottlenecked by digital knowledge work?

TLDR Where does this leave us? LLM agent capabilities (Claude & Codex especially) have crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering and closely related. The intelligence part suddenly feels quite a bit ahead of all the rest of it - integrations (tools, knowledge), the necessity for new organizational workflows, processes, diffusion more generally. 2026 is going to be a high energy year as the industry metabolizes the new capability.

[Gavin Baker @GavinSBaker]

Claude in Excel.

For Microsoft, the beatings will evidently continue until morale improves.

Also fascinating window into AI native vs. software:

Claude evidently only uses Excel as a presentation layer whereas the Microsoft implementation uses Claude to run Excel functions.

[Rohit Nair @__Rohit]

@henrythe9ths AI guide. Thank you

[New York Metro Weather @nymetrowx]

New York City currently has the worst air quality of any city on the planet, and it's not really close. Statistics via @IQAir.

[Andrew Ross Sorkin @andrewrsorkin]

It is a bailout. Not like 2008. But it is a bailout of the venture capital community + their portfolio companies (their investments). That’s the depositor base of SVB. It is the right thing to do in the moment, but there will be ramifications + new regs. VC’s should say thank you

[Bloomberg @business]

The FDIC and the Federal Reserve are weighing creating a fund that would allow the regulators to backstop more deposits at banks that run into trouble following Silicon Valley Bank’s collapse. https://t.co/ghRMd4GOYI

[Bill Ackman @BillAckman]

The gov’t has about 48 hours to fix a-soon-to-be-irreversible mistake. By allowing @SVB_Financial to fail without protecting all depositors, the world has woken up to what an uninsured deposit is — an unsecured illiquid claim on a failed bank. Absent @jpmorgan @citi or @BankofAmerica acquiring SVB before the open on Monday, a prospect I believe to be unlikely, or the gov’t guaranteeing all of SVB’s deposits, the giant sucking sound you will hear will be the withdrawal of substantially all uninsured deposits from all but the ‘systemically important banks’ (SIBs). These funds will be transferred to the SIBs, US Treasury (UST) money market funds and short-term UST. There is already pressure to transfer cash to short-term UST and UST money market accounts due to the substantially higher yields available on risk-free UST vs. bank deposits. These withdrawals will drain liquidity from community, regional and other banks and begin the destruction of these important institutions. The increased demand for short-term UST will drive short rates lower complicating the @federalreserve’s efforts to raise rates to slow the economy. Already thousands of the fastest growing, most innovative venture-backed companies in the U.S. will begin to fail to make payroll next week. Had the gov’t stepped in on Friday to guarantee SVB’s deposits (in exchange for penny warrants which would have wiped out the substantial majority of its equity value) this could have been avoided and SVB’s 40-year franchise value could have been preserved and transferred to a new owner in exchange for an equity injection. We would have been open to participating. This approach would have minimized the risk of any gov’t losses, and created the potential for substantial profits from the rescue. Instead, I think it is now unlikely any buyer will emerge to acquire the failed bank. The gov’t’s approach has guaranteed that more risk will be concentrated in the SIBs at the expense of other banks, which itself creates more systemic risk. For those who make the case that depositors be damned as it would create moral hazard to save them, consider the feasibility of a world where each depositor must do their own credit assessment of the bank they choose to bank with. I am a pretty sophisticated financial analyst and I find most banks to be a black box despite the 1,000s of pages of @SECGov filings available on each bank. SVB’s senior management made a basic mistake. They invested short-term deposits in longer-term, fixed-rate assets. Thereafter short-term rates went up and a bank run ensued. Senior management screwed up and they should lose their jobs. The @FDICgov and OCC also screwed up. It is their job to monitor our banking system for risk and SVB should have been high on their watch list with more than $200B of assets and $170B of deposits from business borrowers in effectively the same industry. The FDIC’s and OCC’s failure to do their jobs should not be allowed to cause the destruction of 1,000s of our nation’s highest potential and highest growth businesses (and the resulting losses of 10s of 1,000s of jobs for some of our most talented younger generation) while also permanently impairing our community and regional banks’ access to low-cost deposits. This administration is particularly opposed to concentrations of power. Ironically, its approach to SVB’s failure guarantees duopolistic banking risk concentration in a handful of SIBs. My back-of-the envelope review of SVB’s balance sheet suggests that even in a liquidation, depositors should eventually get back about 98% of their deposits, but eventually is too long when you have payroll to meet next week. So even without assigning any franchise value to SVB, the cost of a gov’t guarantee of SVB deposits would be minimal. On the other hand, the unintended consequences of the gov’t’s failure to guarantee SVB deposits are vast and profound and need to be considered and addressed before Monday. Otherwise, watch out below.

[Rohit Nair @__Rohit]

Best explanation of the SVB saga #bankRun

[Rohit Nair @__Rohit]

@treiner5 @altcap @theallinpod .@altcap was fantastic on this pod. The macro analysis and the stuff on SBC was absolutely top notch. Really good. @theallinpod need to get him more often

[Greg Ip @greg_ip]

My takeway from India trip: the familiar story of great potential held back by lousy infrastructure, burdensome regulation and inward orientation needs to be retired. Recent economic performance and reforms position it as true economic heavyweight https://t.co/DelEmUu1hN

[FIFA World Cup @FIFAWorldCup]

Have you ever seen anything like it!? 🤯

[The New York Times @nytimes]

A wave of layoffs battering the tech industry after years of growth has left foreign workers on temporary visas in the U.S. scrambling to find jobs — or being forced to leave the country. https://t.co/bAPD6MjUog

[Shital Shah @sytelus]

ChatGPT was dropped on us just bit over 24 hours. It's like you wake up to the news of first nuclear explosion and you don't know yet what to think about it but you know world will never be the same again. Here some interesting snapshots of this "explosion"🧵:

[🇺🇸 Needs too 🇵🇦 @needstoo1]

Lowkey insane

[Rafael Shimunov 🍉 🕎 @rafaelshimunov]

Did Twitter Blue tweet just cost Eli Lilly $LLY billions?

Yes.

[abhishek @abhishek_tri]

What happened in China yesterday is massive. I haven’t seen anything as big in my lifetime. Basically Biden said to American engineers working in China in the semiconductor to either resign or be ready to lose their American citizenship. Everyone resigned. Industry collapsed 🤯