
Interested in marketing analytics, digital marketing and investment services. @salesforce @thecapitalgroup @americanfunds @umaryland
Irvine CA
Joined December 2008
- Tweets1.3K
- Following519
- Followers97
- Likes1.3K
cogitate retweeted
This is one of the worst scientific papers I’ve ever seen.
statmodeling.stat.columbia.e…
cogitate retweeted
One of the lowlights of the Trump administration - and there are MANY - is watching a failed hedge fund manager turned Treasury Secretary disparage a respected journalist who dared to shine a light on a desperate policy of intervention to suppress dollar & yields.👎
@NickTimiraos deserves an apology for this harassment & defamation.
cogitate retweeted
I'm a former Citadel quant who covered power & gas.
There's constant talk about chips & memory, but power is the central bottleneck for AI.
Very few people understand it, so I'm posting a canonical primer on power pricing & data centers: power2026.ai/
cogitate retweeted
What Everyone Missed In Leo’s Blow-Up👇
Leopold Aschenbrenner lost $30 billion (~67%) in a month.
The consensus post-mortem, from the Wall Street Journal to the replies on X, is that a young man used 4-to-1 leverage on concentrated positions and got carried out. While that is true, it does not convey any useful information. Leverage is certainly the reason Leopold lost so much, so quickly. But it is not the reason he lost. Leverage is merely a magnifying glass. It doesn’t pass judgement.
The reason the reason his fund was doomed was because he’s wrong. And no one, anywhere, has explained why.
On the morning of Thursday, July 30, before the opening bell, Situational Awareness LP sold its entire public stock portfolio — the long side and the short side together, roughly $16 billion of it — to Citadel in a single block trade.
Millennium Management and Jane Street bid for the assets. Ken Griffin and Citadel won.
That night, Aschenbrenner wrote to his limited partners. Net performance for the month, unaudited: down 67%. Net performance for the year: still up 80%.
"We let you down this month," he wrote. "We came closer to permanent capital impairment than is acceptable to us."
Six days earlier, on July 24, he had written a different letter. That one reported a 439% net return for the first half of 2026, described the selloff in artificial intelligence stocks as one of the best buying opportunities since early 2025, and invited his investors to wire more money starting August 1. It closed with a postscript: "At times we call out opportunities that seem like a particularly good time to add funds, if you have been waiting for one."
Assets that stood near $45 billion at the start of July finished the month around $10 billion, and roughly half of what remains is a single illiquid private stake in Anthropic.
Leopold is 25 years old. He graduated from Columbia at 19, as valedictorian. He worked at the FTX Future Fund from February to November of 2022, then joined OpenAI's Superalignment team, then was fired in April 2024. Two months after the firing he published a 165-page essay called "Situational Awareness: The Decade Ahead," raised $225 million from Patrick and John Collison, Nat Friedman and Daniel Gross, and started a hedge fund. He had never managed money before.
Situational Awareness was constructed to express only two ideas.
The first conviction: the physical build-out of artificial intelligence — the chips, the memory, the power, the data centers, the neoclouds — was the trade of the decade. The fund's disclosed long positions read like an inventory of the second derivative of the AI boom. Bloom Energy Corporation (NYSE: BE), fuel cells for data centers. Sandisk Corporation (NASDAQ: SNDK) and Micron Technology, Inc. (NASDAQ: MU), memory. CoreWeave, Inc. (NASDAQ: CRWV) and Nebius Group N.V. (NASDAQ: NBIS), rented compute. IREN Limited, Core Scientific, Applied Digital, Riot Platforms, CleanSpark, Bitfarms, Bitdeer — bitcoin miners converting their substations into AI compute.
The second conviction: application software was going to be destroyed by A.I. Not disrupted. Obliterated.
Leo explained why on Dwarkesh Patel's podcast, in June 2024:
"I'm so bearish on the wrapper companies because they're betting on stagnation. They're betting that you have these intermediate models and it takes so much schlep to integrate them. I'm really bearish because we're just going to sonic boom you. We're going to get the unhobblings. We're going to get the drop-in remote worker. Your stuff is not going to matter."
That was the whole thesis. Buy the compute. Short the stuff that runs on the compute.
By CNBC's reporting, the short leg included Adobe Inc. (NASDAQ: ADBE). A 13F does not disclose short stock. It does not disclose swaps. We only know about Adobe because reporters were told… but you can look at the tape and, when you do, it’s clear that Leo was short software in a major way.
Between the June 30 close and the July 29 close — the last session before the block trade cleared his shorts — the two sides of his portfolio did this.
The longs:
· Sandisk: down 55.32%
· Nebius: down 46.33%
· Bloom Energy: down 45.90%
· CoreWeave: down 38.90%
· Micron: down 35.98%
· IREN: down 35.91%
The shorts, over the same 20 sessions:
· Workday, Inc. (NASDAQ: WDAY): up 37.24%
· Adobe: up 28.49%
· Intuit Inc. (NASDAQ: INTU): up 27.64%
· Salesforce, Inc. (NYSE: CRM): up 20.25%
· Veeva Systems Inc. (NYSE: VEEV): up 17.15%
Over that same window the Invesco QQQ Trust fell 10.14% and the SPDR S&P 500 ETF Trust fell 2.32%. Nvidia — the supposed epicenter of the AI trade — fell 5.04%, and finished the full month of July up 0.33%.
This was not an AI crash.
The S&P 500 stayed near its record throughout. This was a violent rotation out of the leveraged, capital-hungry, second-derivative end of the AI complex and into the profitable, cash-generating, asset-light end of it. Which is to say: the market rotated out of exactly what he owned and into exactly what he was short.
Then there is Microsoft.
Microsoft Corporation (NASDAQ: MSFT) closed at $390.54 on Wednesday, July 29. It closed at $451.10 on Thursday, July 30. That is a gain of 15.51% in a single session on 110.2 million shares, against a July average of 37.1 million. Yes, Microsoft reported its fiscal fourth quarter after the close on July 29. But the results were nothing out of the ordinary. Revenue came in at $90.007 billion against a $87.62 billion consensus. That is a 2.7% beat. Earnings were $4.74 per share against $4.21. It was a good quarter. Not a historic one. A 2.7% revenue beat does not add roughly $450 billion of market value to the most widely owned company on earth in six and a half hours. Something else was in that tape.
And the answer is extremely important. Leo blew up quickly because of leverage. But he failed because he is simply wrong.
Aschenbrenner's software thesis rests on a single premise: that a company selling enterprise software is selling the work the software performs. If a model can perform that work, the company is worth nothing.
That premise is what a very smart 25-year-old engineer believes. It is not what anyone who has ever run a business believes.
Nobody buys Microsoft because Microsoft writes the best code. They buy Microsoft because Microsoft is the rail everything else runs on. Active Directory is where your employee identities live. Excel is where your board deck's numbers come from. Teams is where the compliance-recorded conversation happened. Azure holds a FedRAMP High authorization and Department of Defense Impact Level 5 clearance, which means a defense contractor cannot casually swap it out for something cheaper without re-clearing the entire stack with the government.
Veeva runs the customer relationship management and regulatory document systems of the pharmaceutical industry. Nineteen of the top 20 biopharmaceutical companies use Veeva's regulatory information management platform. Those systems are validated under GxP — the good-practice quality regulations that govern anything touching a drug — and 21 CFR Part 11, the Food and Drug Administration's rule for electronic records and signatures. Every major release is formally qualified. When an FDA inspector arrives, the audit trail in that system is the company's defense.
You cannot replace that with a model that is very good at writing code. You would have to re-validate a decade of regulated records, in front of a regulator, on a system with no track record, to save a fee that rounds to nothing in terms of the cost of building a new drug.
How small a fee? Veeva's licensing runs somewhere between roughly $1,800 and $6,600 per sales representative per year. A fully loaded pharmaceutical sales rep costs the employer between $134,000 and $219,000 a year. The software is 1% to 5% of the cost of the person using it.
Microsoft raised the price of a Microsoft 365 E3 seat from $36 to $39 per user per month on July 1 of this year, and E5 from $57 to $60. Add Copilot at $30 and a fully loaded E5 seat costs $1,080 a year. Against a knowledge worker costing $75,000 to $120,000 all-in, that is roughly 1% of the employee.
This is the part the compute maximalists cannot see. These companies are not selling labor. They are selling the rails on which labor runs, at a price so far below the value created that the buyer never bothers to negotiate hard, and with switching costs so high that the buyer could not leave even if he wanted to.
Do people try to leave? Constantly. And they almost always fail. (Ask me how I know!)
Panorama Consulting Group's tracked studies of enterprise resource planning replacements put average cost overruns at 189% across industries. Gartner projects that by 2027, more than 70% of recently implemented ERP initiatives will fail to fully meet their original business goals. Ripping out a core enterprise system is one of the most reliably disastrous things a large company can attempt, and it was true before anyone had heard of a transformer model.
The incumbents are not being disintermediated by artificial intelligence. They are selling it!
Microsoft passed 30 million paid Copilot seats in the June quarter, up from 15 million in January. Tech wizards like Leo hate copilot. Just like they hated Windows ’97. And everything else Microsoft has ever built. So what? Accenture alone bought 740,000 of them. Bayer, Johnson & Johnson, Mercedes-Benz and Roche have each deployed more than 90,000. Microsoft's commercial remaining performance obligation — contracted revenue not yet recognized, which is the closest thing software has to a railroad's signed freight contracts — stands at $678 billion, up 84% year over year!
Adobe's AI-first annual recurring revenue passed $500 million in the quarter ended May 2026 and tripled year over year. Salesforce's Agentforce went from $800 million of annual recurring revenue in the January quarter to $1.2 billion by April, up 205%. Veeva is giving its AI agents away free inside Vault CRM through 2030, which is the single most revealing data point in the set: Veeva does not need to monetize AI, because Veeva's moat is the validated record, not the intelligence applied to it.
Aschenbrenner thought AI would eat the applications. Instead the applications are selling AI as an upsell on top of a subscription the customer cannot afford to cancel – because it costs nothing compared to the value it delivers.
These software companies are computing toll booths: they’re what enterprises pay to implement compute. And, as compute gets cheaper, they will generate vastly more revenue, not less. The proof is sitting there in their earnings and cash flows: they’re riding on lower and lower cost of compute, which makes their business more and more efficient.
· Adobe: 36.6% operating margin, 35.6% return on invested capital, capital expenditure of $179 million on $23.8 billion of revenue — 0.75% — and $9.85 billion of free cash flow.
· Veeva: 28.7% operating margin, 68.5% return on invested capital, a 44.3% free cash flow margin, and effectively no capital expenditure at all.
· Salesforce: $41.5 billion of revenue, roughly $14.4 billion of free cash flow, capital expenditure of about 1.4% of revenue, and $72.4 billion of contracted backlog.
· Intuit: $18.8 billion of revenue, roughly $6.1 billion of free cash flow, $124 million of capital expenditure.
Veeva earns 68 cents a year on the dollar. And invests nothing it growing its business.
Adobe currently trades at about 11 times trailing earnings. Salesforce at about 13. Intuit at about 14. These are the multiples of a dying industry, applied to businesses converting a third to nearly half of every revenue dollar into free cash.
This enormous mispricing was manufactured by people who like Aschenbrenner, believed these businesses were doomed. But they aren’t.
And that’s not all.
Aschenbrenner assumed that because a technology is transformative, the capital that builds it will earn its cost.
There is no relationship between those two things. In fact, it’s more likely not to be true.
Leo’s own essay contains the tell: "Over the past year, the talk of the town has shifted from $10 billion compute clusters to $100 billion clusters to trillion-dollar clusters. Every six months another zero is added to the boardroom plans."
He wrote that as a bull case. But it isn’t. That is a recipe for a financial disaster.
Amazon.com, Inc. (NASDAQ: AMZN) spent $131.8 billion of capital expenditure in 2025 against $139.5 billion of operating cash flow. That is 94.5% of everything the business generated, poured back into the ground, in a single year. Its 2026 cap ex guidance is $220 billion.
Alphabet Inc. (NASDAQ: GOOGL) spent $91.4 billion in 2025, 55.5% of operating cash flow, and guides to $195 billion to $205 billion this year.
Meta Platforms, Inc. (NASDAQ: META) spent $72.2 billion, 62.4% of operating cash flow, and guides to $125 billion to $145 billion.
Microsoft spent $115.9 billion in the fiscal year that just ended, against $182.9 billion of operating cash flow. Capital expenditure was 34.9% of revenue, up from 18.1% two years earlier. Free cash flow fell to $67.0 billion from $74.1 billion in fiscal 2024, on revenue that grew by more than a third over the same span. Microsoft is running harder and generating less cash. That is what a huge capital cycle does even to the best business in the world.
Moody's projects hyperscaler capital expenditure of $785 billion in 2026 and close to $1 trillion in 2027, funded in part by roughly $175 billion of debt issuance this year. Where will the money come from…?
Oracle: fiscal 2026 capital expenditure of $55.7 billion, free cash flow of negative $23.7 billion, capital expenditure at 82.6% of revenue, long-term debt up from $76.3 billion to $124.7 billion, and $248 billion of future data-center lease obligations not yet on the balance sheet.
CoreWeave: $5.13 billion of 2025 revenue, $14.9 billion of capital expenditure, negative $7.25 billion of free cash flow, net debt at 8.1 times EBITDA, term loans at 11% to 15%, a weighted-average short-term borrowing rate of 12.3%, and a $1 billion private placement in April 2026 at 9.75%.
Meta's Hyperion campus in Louisiana is financed through a special purpose vehicle in which Blue Owl Capital holds 80% and Meta holds 20%, funded by $27.294 billion of senior secured notes at a 6.581% coupon maturing in 2049. The noteholders have no pledge on the physical data center. Their credit is Meta's promise to pay rent starting in 2029, plus a residual value guarantee. Twenty-seven billion dollars of debt, secured by a lease, sitting off the balance sheet.
And… like the EU’s finance minister explained two decades ago… “when it gets serious, you have to lie.”
Microsoft extended server useful lives from three years to four, then to six, adding about $3.7 billion to fiscal 2023 operating income. Alphabet did the same, adding about $3.0 billion. Amazon added about $2.5 billion in 2024. Meta added $2.59 billion in 2025. Oracle added $573 million. Every one of those is a non-cash increase in reported profit produced by an assumption about how long a chip stays useful. It’s a lie.
But not everyone is lying. Effective January 1, 2025, Amazon shortened the useful life of a subset of its servers and networking equipment from six years back to five, citing, in its own 10-K, "the increased pace of technology development, particularly in the area of artificial intelligence and machine learning." That cost it $1.4 billion of additional depreciation and $1.0 billion of net income.
Amazon is the operator with the longest and hardest-won experience running data centers at scale, and Amazon is the one telling you the hardware wears out faster than the schedules assume.
How could all of this spending possibly pay off?
Bain & Company's global technology report puts it at roughly $2 trillion of annual artificial intelligence revenue by 2030, and calculates that even if every dollar of on-premise IT budget shifted to the cloud and every dollar of AI productivity savings were reinvested, the industry would still be about $800 billion short. Sequoia Capital's David Cahn, who has been running the same arithmetic since 2023, has escalated his estimate from $200 billion to $600 billion to roughly $840 billion.
Against that: OpenAI's audited 2025 revenue was $13.07 billion, with an operating loss of $20.92 billion. Anthropic's 2025 revenue was $10 billion. Combined, $23 billion.
And of every dollar spent on Nvidia systems, roughly 72 to 75 cents is Nvidia's gross profit. Data center is now 88% of Nvidia's revenue. The margin is not in the build-out. The margin is in selling to the build-out.
What’s about to happen is obvious, because it has happened before.
Between 1865 and 1873 the United States built the most consequential physical network in its history and destroyed an enormous amount of capital doing it.
Track mileage went from 35,085 miles in 1865 to 52,922 in 1870 to 74,096 by 1875. Construction peaked at 7,439 miles laid in 1872. Railroad capital reached roughly $4.5 billion at a time when the entire banking system's capital was $720 million and the federal debt was $2.3 billion. In January 1870, of 896,596 shares traded on the New York Stock Exchange, 781,340 — 87% — were railroad shares. From 1870 to 1874, roughly 70% of all railroad securities issued in London were American. American rail bonds paid 6.5% when British consols paid far less, and European capital came for the yield.
Every argument you hear today was made then, too. The railroads will transform the country. Yep, they did compress distance and cost of transportation in a way that seemed impossible only a few years earlier. And it didn’t make any difference.
On September 18, 1873, Jay Cooke & Co. failed. Cooke had contracted to place $100 million of Northern Pacific 7.3% gold bonds, but sold less than $20 million. He ended up effectively owning 75% of the railroad he was supposed to be financing. And it failed. The New York Stock Exchange closed for ten days — the first closure in its history.
By 1876, 134 railroads were in default on $500 million of bonds out of roughly $2 billion outstanding. By 1877, 20% of American railroad track mileage was in receivership. European investors are estimated to have lost around $600 million between 1873 and 1879.
A very large fraction of the capital that built the American rail network was lost.
And where the roads survived, competition took the returns. Revenue per ton-mile fell from 1.88 cents in 1870 to 0.73 cents in 1900, a decline of about 61%. Rate wars on the New York-to-Chicago corridor drove the through rate from $1.88 down to 25 cents, then 20 cents, and no pooling agreement stabilized the worst of it until late 1885.
Every additional mile of track made the network more valuable to America and less valuable to the men who had paid for it.
The AI build-out will have the same problem – but it will be much, much worse. Compute will be a pure commodity.
Nobody disputes that the models are transformative. The problem is, that’s true of all of them.
Which of the second-derivative names Aschenbrenner owned has route control, like a monopoly railroad? Bitcoin miners with retrofitted substations? Rented compute resold at a spread? Memory, an industry that has never once earned its cost of capital through a full cycle? Those are not toll booths. Those are the Northern Pacific just before bankruptcy.
The railroads made a fortune – but not for their investors.
Adams Express Company was incorporated in 1854 with $1.2 million of capital. It did not own a single mile of track. It bought space on other men's trains and moved parcels, money and valuables on them. By 1866 its capital was $10 million and it was paying an 8% dividend quarterly. By 1875 its capital was $12 million. It paid an unbroken $8 per share annual dividend from 1869 forward — straight through the depression that put a fifth of American rail mileage into receivership, and straight through the next one in the 1890s.
American Express Company (NYSE: AXP) declared a $6 dividend in 1869, cut it to $3 in the depression year of 1877, restored it to $6 by late 1881, and held it there for the rest of the century. An 1888 board report showed ten-year net earnings of $26.24 million.
By 1890, the express companies were handling more than 115 million packages a year over 174,535 miles of railroad and steamship routes. And they didn’t own a single locomotive or a single boat.
Pullman's Palace Car Company was organized in 1867 with $1 million of capital. It did not own track either. It owned the sleeping cars and leased them to the railroads. Capital grew to $36 million by the early 1890s with nearly $25 million of accumulated surplus. Dividends ran 9.5% to 12% from 1867 to 1871 and 8% annually for decades after. In 1879, with 464 cars out on lease, it earned gross revenue of $2.2 million and net profit of almost $1 million.
Pullman put out $1 million of equity and earned $1 million a year on a network that cost other people billions and bankrupted a third of them.
Adams Express converted itself into a closed-end investment fund in 1929 and is still listed today as Adams Diversified Equity Fund (NYSE: ADX). The company that rented space on the railroads outlived almost all of them.
I’d bet a lot of money that Leo had never heard of any of these businesses.
But for people who are experienced in putting capital at risk, the pattern is not subtle or hard to understand. When an economy builds an expensive new network, the capital that builds the network earns a poor return because competition, obsolescence and overbuild strip it away. The businesses that ride on the network at near-zero incremental capital cost, and that own the customer relationship, the data or the standard, keep the profit.
I’ve seen this entire act before, during my career.
In the five years after the Telecommunications Act of 1996, carriers poured more than $500 billion into fiber, switches and wireless networks. By the early 2000s no more than 2% of North American long-haul capacity was in use. Global Crossing raised roughly $20 billion, built 100,000 miles of undersea fiber, filed for bankruptcy in January 2002, and saw its assets change hands for about $250 million — roughly 1.25 cents on the dollar of invested capital. WorldCom filed six months later, at the time the largest bankruptcy in American history.
Who got the value? Google, Amazon and Netflix, which built businesses on top of bandwidth that had become nearly free because somebody else had already gone bankrupt providing it. By 2018 and 2019, Google and Facebook were funding roughly four of every five dollars of new transatlantic cable investment — buying the rails only once the rails were cheap and only once they owned the applications that made the rails worth owning.
Leopold Aschenbrenner is not stupid. He is the opposite of stupid, which is part of the problem. He is a brilliant technologist who has never had to make a payroll, never had to explain to an auditor why the electronic records changed, never had to decide whether to spend eighteen months and $40 million ripping out a working system to save $200,000 a year in license fees.
He looked at enterprise software and saw code. A businessman looks at enterprise software and sees the thing his company cannot operate without for a single day, priced at 1% of the employee who uses it, backed by a validated audit trail he would have to rebuild from scratch in front of a regulator, and running on a contract he signed for three years.
An investor who has read a balance sheet from 1874 sees $220 billion of annual capital expenditure, an 8-times-levered reseller of rented compute borrowing at 12%, $27 billion of data-center debt hidden in a special purpose vehicle, and useful-life assumptions that the most experienced operator in the business is quietly walking back.
The kid believed the technology determines the return. But it never has.
It’s the capital structure that determines the returns: who controls the standards, who controls the customer, and who owns the data? Yes, the A.I. models will change everything. But that does not mean the people building the machines will be paid for it.
The money will be made where it was made in 1874 and again in 2004: by the toll booths riding on top of somebody else's ruinous capital expenditure.
cogitate retweeted
Today we reduced headcount by 22%. The business is the strongest it's ever been. So I think it's important to be direct about what I'm seeing and why.
First, I made this decision and I own it. I did it because the way to operate at the highest level of productivity is changing, and to win the future, ClickUp needs to change with it.
Second, this wasn't about cutting costs. Most savings from this change will flow directly back into the people who stay. We'll be introducing million-dollar salary bands. If you create outsized impact using AI, you'll be paid outside of traditional bands.
Most importantly, I have the deepest gratitude for those affected. We're doing this from a position of strength specifically so we can take care of people properly. Everyone affected receives a package aimed at honoring their contributions and easing the transition.
I only see two options: wait for this to play out gradually in the market or be honest about what I'm seeing and act proactively.
THE 100X ORGANIZATION
The primary change is that we're restructuring around what I call 100x org. The goal is 100x output. The roles required to build at the highest level are fundamentally different than they were a year ago.
Incremental improvements to existing systems won't get us there. We need new ones. That means creating enough disruption to rebuild rather than iterate on what's already broken.
The common narrative is that AI makes everyone more productive. It doesn't. Many of the workflows of today, if left unchanged, create bottlenecks in AI systems.
These roles will evolve. But waiting for that to happen naturally means falling behind now.
The 100x org is actually heavily dependent on people - infinitely more than today. This is only possible with 10x people that have embraced and adopted new ways of working.
THE BUILDERS, AGENT MANAGERS, AND FRONT-LINERS
— THE BUILDERS: 10X ENGINEERS
I don't think most companies have internalized what's actually happening with AI in engineering. The common narrative is that AI makes all engineers more productive. That may be true in isolation, but at an organization level - that is the farthest thing from reality.
Here's what we've validated recently at ClickUp: the great engineers, the ones who can orchestrate, architect, and review, are becoming 100x engineers. They're not writing code. They're directing agents that write code. The skill is judgment.
AI makes the best engineers wildly more productive, and everyone else using AI slows these engineers down.
Think about it - the bottlenecks are (1) orchestration - telling AI what to do, and (2) reviewing - what AI did. Everything is leapfrogged and no longer needed.
So who do you want orchestrating and reviewing code?
And how do you want your best engineers to spend their time?
If your best engineers are spending time reviewing other people's code, then this is inherently an inefficient bottleneck. These engineers can review their agent's code much faster than reviewing human code.
The new world is about enabling your 10x engineers to become 100x.
The wrong strategy is to push every engineer to use infinite tokens. Companies doing this are celebrating 500% more pull requests. But customer outcomes don't match the volume of code being generated.
I call this the great reckoning of AI coding, and every company will face this soon if not already.
More code is just another bottleneck to the best engineers, and ultimately to your company's impact as well.
— THE BUILDERS: 10X PRODUCT MANAGERS
Product management and design roles are merging.
Designers that have customer focus, become more like product managers.
And product managers that have intuition for UX become more like designers.
The bottleneck of user research is gone. It takes us just one mention of an agent to kickoff research and analyze results.
The bottleneck of product <> design iteration is also gone. The product builder iterates on their own, along with agents and skills that ensure alignment with quality and strategy.
Also controversial today - I believe that the wrong strategy is to have your PMs shipping code - that just introduces another bottleneck that the best engineers will waste their time on.
To be clear, PMs should be coding but they should do this in a playground to iterate, validate, and scope. That code should not go to production.
Everything outside of managing systems, orchestrating AI, and reviewing output becomes a bottleneck.
That's why the other roles that are critical along with these are the systems managers (to reduce bottlenecks) along with a bottleneck you can't replace - customer meeting time.
— THE SYSTEM MANAGERS
Ironically, the people that automate their jobs with AI will always have a job. They become owners of the AI systems - agent managers. We have many examples of these people at ClickUp.
The underlying systems in which we operate are absolutely critical to get right. I think most companies are delusional to think they can iterate on existing systems and compete in this new world.
You must create enough disruption so that old systems are deprecated entirely. If there's any definition for 'AI native' that's what it is.
— THE FRONT-LINERS
In a world that will become saturated with AI communication, the human touch will matter more than anything to customers.
This is a bottleneck that you shouldn't replace - even when agents are high enough quality to do video meetings.
One-on-one meeting time with customers is something that shouldn't be automated. The systems around the meetings should be - so that front-liners spend nearly 100% of their time with customers.
REWARDING 100X IMPACT
In a world where companies are able to do so much more with less, where does that excess money go?
In our case, much of the savings in this new operating model will flow directly back to those that enabled it.
We must reward people that create productivity accordingly. This aligns incentives on both sides. Plus, in a world where your best people create 100x impact, you can't afford to lose them.
You should aim to retain these employees for decades. The context they have and their ability to efficiently orchestrate and review will be nearly impossible to replace.
Compensation bands of today should be thrown out the door. We're introducing $1 million cash/year salary bands with a path available to nearly everyone in the company if they produce 100x impact by creating or managing AI systems.
THE FUTURE
Nearly every company will make changes like these. The ones that do it proactively will define what comes next.
The future is not fewer people. It's different work, new roles, and better rewards for those who embrace it. We're already seeing entirely new roles emerge, like Agent Managers, that didn't exist a year ago.
ClickUp is positioning to lead this shift, not just internally, but for our customers too. I've never been more certain about where we're headed.
cogitate retweeted
Famously (there is a beautiful Works in Progress piece on this) in 2016, Geoffrey Hinton told an audience in Toronto that medical schools should stop training radiologists, since AI would soon outperform them at reading scans. Ten years later, there are more radiologists than ever, and they earn more than they did then.
Hinton was right about the task, but he was wrong (so far!) on the future of the radiology profession. Times have never been better for them. The gap between those two claims, the difference between tasks and jobs, is the subject of a paper I have written with Jin Li and Yanhui Wu, and that we release today: "Weak Bundle, Strong Bundle: How AI Redraws Job Boundaries." (Very relatedly we are also finishing the first draft of our book "Messy Jobs" on AI and Jobs!! You will be the first to hear).
We start from the observation that the growing literature on AI and labor markets measures the AI shock by task exposure: people count how many tasks AI can perform in a given occupation AI can perform, and infer that more exposure means more displacement. Eloundou et al. published a paper in Science in 2024 that started this literature, and many follow the same logic. The inference they make is that the more exposed tasks, the worse the outcomes.
This is incomplete, because labor markets price jobs, not tasks. A radiologist does not just sell image classification, but does many other jobs: triages cases, communicates with other physicians, trains residents, makes the difficult decisions, and signs a diagnosis. The market buys a bundled service. The question AI poses is not whether it can do one task inside the bundle. The question is whether that task can be pulled out.
Thread (1/3)
dropbox.com/scl/fo/689u1g785…
cogitate retweeted
Software horror: litellm PyPI supply chain attack.
Simple `pip install litellm` was enough to exfiltrate SSH keys, AWS/GCP/Azure creds, Kubernetes configs, git credentials, env vars (all your API keys), shell history, crypto wallets, SSL private keys, CI/CD secrets, database passwords.
LiteLLM itself has 97 million downloads per month which is already terrible, but much worse, the contagion spreads to any project that depends on litellm. For example, if you did `pip install dspy` (which depended on litellm>=1.64.0), you'd also be pwnd. Same for any other large project that depended on litellm.
Afaict the poisoned version was up for only less than ~1 hour. The attack had a bug which led to its discovery - Callum McMahon was using an MCP plugin inside Cursor that pulled in litellm as a transitive dependency. When litellm 1.82.8 installed, their machine ran out of RAM and crashed. So if the attacker didn't vibe code this attack it could have been undetected for many days or weeks.
Supply chain attacks like this are basically the scariest thing imaginable in modern software. Every time you install any depedency you could be pulling in a poisoned package anywhere deep inside its entire depedency tree. This is especially risky with large projects that might have lots and lots of dependencies. The credentials that do get stolen in each attack can then be used to take over more accounts and compromise more packages.
Classical software engineering would have you believe that dependencies are good (we're building pyramids from bricks), but imo this has to be re-evaluated, and it's why I've been so growingly averse to them, preferring to use LLMs to "yoink" functionality when it's simple enough and possible.
cogitate retweeted
"You went to IIMA? What did you learn there?"
This question popped up late last year during one of my client pitch calls. I was talking to a smart young tech fellow, who had just raised money for his company. And usually these calls are about getting to know each other, what they do, what I do, how we can work together, communications, content, stories etc.
So... this question was unusual.
I am not a big credentials person. But when you are running your own business, every little helps, right?
Anyway, it made me think. And I thought: You know what? I should share this with my Twitter friends.
***
IIMA teaches you a lot about many things. And your mileage will vary. I loved it.
But two, ostensibly tiny, classroom experiences have really stuck with me from my time there from 2003-2005.
The first was the Arun Icecreams case study. (IIMA uses the case study methodology a lot. I don't think I appreciated this as much as I should have at the time.)
This case was a sweeping history of the company from its inception in 1970 all the way to an inflection point in 1997 where the company's leadership now had to make some business decisions in the face of rising competition from people like Unilever. Our job in the class was to discuss and debate options.
Two decades later I have zero memory of the conclusions of that session. But I remember one particular question that the professor asked to kick things off. It had to do with this section on page 1 of the case study. Let me paste the text here. (You can Google up the whole thing.)
Slightly long excerpt. But there is a point to this.
"Chandramogan, son of a vegetable wholesaler from the South Indian state of Tamil Nadu, set up Arun Ice Cream in 1970 in Madras (now re-named Chennai), essentially motivated by the urge to "do some thing". After his college studies were discontinued at the pre-university stage, Chandramogan agonised over several weeks about starting some business without being quite able to narrow down to any specific line, mainly because of heavy investments entailed. While driven by an urge to succeed as a businessman, he did not quite know how to go about setting up a business. It was his maternal uncle who suggested the business of ice cream. Investing Rs. 15,000 as his own capital and raising another Rs. 21,000 by way of a bank loan, he set up a small ice candy unit in a rented premises adjacent to his uncle's retail textile outlet. From a quick survey around the Madras market it appeared to Chandramogan that there were about 350 small-time ice candy manufacturers like himself competing in the low end of the market. These were offering no competition to the up-market segment dominated by the leading brands Dasaprakash, Joy and Kwality. Like the "others in the crowd", Chandramogan was also selling his Arun brand ice candies for 10 paise and 15 paise a piece predominantly through street-vendors. Thanks to its prominent location in a busy locality, Arun also quickly began attracting walk-in customers. The fact that one could get "fresh" ice candies right across the factory counter was a major selling point in promoting in-factory sales. In the very first year of operations, Chandramogan recalls, Arun clocked a turnover of about Rs. 150,000 and profit of about Rs. 40,000."
And the question posed to the class was: "Why did Chandramogan choose that particular location to start the business?"
This was a location in Royapuram. And if I remember correctly, it was in a busy commercial area next to a flyover. The details are not super relevant as you will soon see.
With all the alacrity of young MBA students, who all wanted to work at Goldman Sachs or McKinsey, we dove into the location question.
Because of footfall! Because of traffic! Maybe it had uninterrupted power supply? Maybe he had access to manpower? Maybe there were other ice cream shops nearby? One guy even suggested it was because Royapuram was very hot, and maybe that would make people buy more icecreams.
The professor, who was clearly having fun, kept provoking us. And eventually he said: "Ok good. Now let me tell you my perspective on what really happened?"
This is a bit of a cheat. But because many of our cases were written by our own faculty, they sometimes had more info than was obvious from the text. And part of our job was to tease this out? Anyway. I will pause on Arun Icecreams here. And I want you to think about his question: Why did Chandramogan start the first shop in that location in Royapuram.
***
Second story. One of the final courses I did was one on Entrepreneurship, that was run by the venerable Sunil Handa. It was a bewildering, often bizarre course. And the point was to make a room full of campus-placement obsessed fellows think about running their own businesses. (Please remember, this was way back in 2005, when all this VC-funded startup frenzy was very very nascent. The default thing to do was very much get a campus job.)
Right at the end of the course Sunil Handa told us that it was time to grade our performance on the course. He said there would be no exam, no tests, no presentations. Nothing. We were all handed a piece of paper. And we were told grade ourselves on the standard IIMA Scale. A, B+, B and so on. (Was there an A+? I have forgotten.) On what basis, we asked. Whatever basis, he said. You decide. I don't care. Whatever you grade yourselves I will accept as your grade for this course.
We all graded ourselves and handed the slips in. The next week, the last session of the course, Prof. Handa bid us all farewell and good tidings. And then gave us a distribution of the scores. "Most of you gave yourselves a B of some sort," he said. And it turned out that exactly one guy gave himself the highest possible score. Nobody else. And the scores had very little correlation with performance. Most of us thought about attendance and participation and field trips and so on, and scored ourselves aiming for some notion of "fairness". Something like that.
He said: "You guys need to realize that entrepreneurship is not primarily about fairness or justice or anything. Entrepreneurship is about making the most of the opportunity given to you. When someone gives you a chance, for god's sake, take it. You should have all given yourself an A+. Never talk yourself out of success. Go you fools, and never forget this lesson!"
I embellish, of course. But that moment remains etched in stone on my heart. I gave myself a B+.
Back to Arun Icecreams.
***
Professor: "So guys. Let's talk about the uncle figure."
"What do you think the maternal uncle is thinking to himself? Look at this guy, my nephew. He has dropped out of college. He wants do something but doesn't know what. I had to tell him what to do. Plus he has now taken a loan and put in some of his own money. Maybe I have given him some money myself? I am not letting that guy out of my sight. I want to make sure I can keep an eye on my nephew, in case he screws this icecream thing up."
And that is why, the professor told us, he opened the shop right next to his uncle's. His uncle found the location for him. So that he can keep an eye on this nephew's shenanigans.
"Business is not always location, footfall, tactics, and 2x2 matrices and stuff like. Often business is just human beings doing human being things. With simple human incentives and motivations. Never ignore the human aspects of business. Always keep the individuals, their motivations, fears, excitements, tendencies, and eccentricities in mind. Ask the human question first, apply the framework second."
***
Two decades later, a day doesn't go by when I don't think of those two lessons.
When I talk to clients I am always provoking them to tell me why... they are in Royapuram. And I have to constantly tell myself that there is a time to be humble, and there is a time to be your own champion.
Many thanks for your attention. Cheers. And have a nice day. Oh, and have a great 2026.
I give this note an A+.
My annual letter:
danwang.co/2025-letter/
This year I discuss corgis, compute, and Cold War; the Texas State Fair; DSA; Neue Sachlichkeit; disfiguring the physical past and the end of history; Germanic obedience; Antichrist; wisecracks; Pascal’s Wager; romantasy; and croissants.
cogitate retweeted
The fifth anniversary of a viral histogram
statmodeling.stat.columbia.e…
In Search of the AI Bubble’s Economic Fundamentals by William H. Janeway @ProSyn prosyn.org/jdf3oHO
cogitate retweeted
On the trail of Spain's lost multicultural history in Seville, by @pallaviaiyar open.substack.com/pub/pallav…
























