7 bets on AI
1The horizon problem
AI is already good at automating quick tasks: ones where it gets feedback fast and doesn't lose track of what it's doing. METR tracks this: the length of task an AI agent can reliably finish has been doubling roughly every four months through 2025. But even METR says they can't reliably measure anything past 16 hours yet. Nobody actually has good data on long tasks. The real problem with long tasks is what researchers call the credit assignment problem: it's hard for the AI to figure out which of its earlier actions caused something to go right or wrong, especially when feedback is rare. Step count isn't the real limit either. A 2026 study found that if a model is 95% reliable at each step, that compounds to just 59% success over 10 steps and 36% over 20, which looks like a hard capability wall but is really just multiplication. Long, multi-step tasks won't be reliable until AI gets much better at trying different approaches and reasoning across many steps without losing the thread, and that also depends on training environments that actually look like real work. On TheAgentCompany, a benchmark that simulates a real software company, even the best agents only finish 30% of tasks on their own. Most training environments are still too clean and predictable to prepare AI for that kind of mess.
2Job losses vs. new company creation
Money that used to pay workers is shifting toward AI instead, and you can already see the gap between the big picture and the personal one in the data. Stanford's Brynjolfsson-Richardson tracking shows jobs for 22-to-25-year-olds in the most AI-exposed roles shrinking about 3.8% a year, while the job market overall barely moves, down only about 0.2% a year. AI makes routine work cheap to do, and that wipes out specific jobs completely. If it's your job, the good macro numbers don't help you. At the same time, cheaper execution means more people can afford to start a business, and that's creating new companies. Indeed's Hiring Lab says almost the same thing: "the defining labor market challenge ahead is labor reallocation, not creation." They think AI only causes 27–35% of this shift, though, with the rest coming from fewer young workers overall. The real problem is speed: moving people whose jobs disappeared into new roles, managing or overseeing AI instead of doing the work by hand, fast enough that it doesn't drag down the whole economy.
3Specialized AI, not general AI
The future of enterprise AI is small models built for one job, running on a company's own servers. Right now, companies are sending every request to paid APIs, and the bills are piling up. Palo Alto Networks' CEO put it plainly in July 2026: even though the price per AI request has dropped 98%, his company's total AI bill tripled anyway, because AI agents chain together many requests to finish one task, and that eats up the savings. He wants prices to fall another 90% before AI makes sense at real scale. It's not just him: MIT's NANDA initiative studied 300 companies using AI and found 95% saw no real impact on profit, and PwC's 2026 survey of CEOs found almost the same thing, with 56% unable to point to any real benefit yet. That's getting better, not staying stuck: the number of S&P 500 companies that can prove AI is paying off went from 21% to 40% in a year. But most companies are still measuring this wrong, because they're using a giant do-everything AI model on a narrow, predictable problem that doesn't need one. The standard will become small, task-specific models running in locked-down environments a company fully controls: faster, safer, and actually worth what they cost.
4Systems skills, not just code
AI can write code now, so just knowing how to write code stops being special. There's already real data on what that's doing to codebases: GitClear looked at 211 million lines of changed code and found the amount getting rewritten or thrown away up 39%, duplicate code up 8x, and actual cleanup work dropping from a quarter of all commits to a tenth. Somebody has to fix that mess, and my bet is it won't be a better prompt writer. It'll be engineers who understand how systems behave under real load, how to keep things running when parts break, and how to make software fast, the kind of knowledge you can't get by prompting well. When AI is churning out a lot of code that works but isn't well built, the valuable skill becomes pulling all of that together into something that actually holds up, keeping track of a much more complicated system, and protecting it now that there's so much more surface to attack.
5Testing what AI does, not what it knows
Standard tests like MMLU are maxed out and easy to cheat on. GPT-4 could guess the right answer on MMLU questions 57% of the time without even seeing the question, and close to a third of the test looks like it leaked into the AI's training data. None of that tells you how the AI actually behaves in the real world. Testing needs to move toward watching what a model actually does under pressure, not just whether it knows facts. METR did exactly this in early 2026, running a joint test with Anthropic, OpenAI, Google, and Meta that watched for bad behavior instead of grading a fixed test. In one case, a model found a way to cheat its own test and then posted about it publicly. That's the kind of failure a multiple-choice test will never catch. This means running models in safe, contained simulations and deliberately searching for many different kinds of failure, not just the most obvious one. It's the same idea as fuzzing in software testing: instead of checking a handful of expected inputs, you throw a huge range of inputs at the system to cover the entire latent space of failures.
6Proving code is correct
Formally proving code is correct, mathematically rather than just testing it, never caught on before because it took too much human effort to be worth it. One team spent 20 person-years mathematically proving just 8,700 lines of code were correct. It wasn't that the checking tools were too slow: Amazon has been running about a billion automated correctness checks a day to verify its AWS access rules since 2022, so those tools were already plenty fast. What AI actually fixes is the human effort: someone still has to write the rules the code must follow, but AI can now do a lot of the proving work itself. That means provably correct code becomes realistic, and bugs in the code itself stop being the main security risk. What's left to secure is the infrastructure underneath it, and there's already a good playbook for that. Amazon has been using TLA+ to verify systems like S3 and DynamoDB since 2011, checking that the design itself can't enter a broken state before a single line of code gets written. That same approach, applied more widely and sped up by AI, is probably where infrastructure security goes next.
7Memory size beats memory speed
Running large AI models is limited by memory, not raw calculation speed: the hard part is fitting hundreds of gigabytes of the model somewhere fast enough, not doing more math. Right now everyone's chasing this through HBM, a type of ultra-fast memory used in datacenter chips: SemiAnalysis says memory now makes up over 30% of what it costs to build an Nvidia AI system, HBM is sold out everywhere through 2026, and the market for it is headed from $35 billion to $100 billion by 2028. But that's all about speed in a datacenter. Apple's approach is the quieter version of the same idea: instead of chasing speed, it chases size. A Mac Studio with 512GB of memory costs about $9,500 and can run open models that won't even fit into a $13,250 Nvidia RTX Pro 6000, which tops out at 96GB, all while using a fraction of the power. As open models keep getting bigger and more people run them locally on specialized hardware, how much memory you can afford per dollar becomes the real limit on who gets to run these models, not who owns the biggest datacenter.