Topics

AI Infrastructure

28
Talks
50
Speakers
30
Organizations

Latest talks

The Dark Factory Argument: swyx on Agent Supervision at Build 2026
The Dark Factory Argument: swyx on Agent Supervision at Build 2026

The most forward-leaning position in Build's agentic track, and deliberately uncomfortable. Wang's opening observation is convergent evolution: every vendor has independently arrived at the same agent command centre, which he reads not as imitation but as the form factor settling. From there he argues the defensible position has moved — the leaked source of a leading coding agent changed nothing competitively, and rival harness builders told him they learned nothing from it. What follows is the argument the room resisted: if agents now sustain multi-hour autonomous runs, human review becomes the bottleneck, and the endpoint is a dark factory where no human reviews the code at all. He does not present this as desirable. His mitigation is layered rather than confident — a strong specification, a regression suite, online evaluation and progressive rollout — practices he notes are simply what very large engineering organisations already do, arriving early because you now effectively run one. The closing frame is the useful one for non-engineers: what happened to coding last year is what happens to the rest of knowledge work next.

Microsoft Build

Why 40% of Agent Projects Get Cancelled, and Why It Isn't the Model
Why 40% of Agent Projects Get Cancelled, and Why It Isn't the Model

The session opens with an analyst projection that over forty per cent of agentic projects will be cancelled by 2027, and the diagnosis offered is the useful part: none of these are model problems, they are runtime problems. Two failures make the case. An agent that restarts loses context, cache and intermediate state and pays the setup cost again, which turns a restart during a long-running task into total loss of accumulated work exactly when the value is highest. And an agent running as trusted code on a developer's machine inherits that environment — SSH keys, browser cookies, everything — which is the arrangement most agent development actually uses and does not survive a process running unattended against a prompt someone else influenced. The reframing is testable against the failures people describe, none of which are failures of intelligence.

Microsoft Build

Nadella's Argument: Enterprises Stop Consuming the Frontier and Join It
Nadella's Argument: Enterprises Stop Consuming the Frontier and Join It

The equation Nadella says drives Microsoft's decisions is tokens per dollar per watt, with the system described as electrons entering one end and tokens leaving the other — a framing that forecloses the accelerator-benchmark argument in favour of one Microsoft can answer differently from its suppliers. Two claims sit beside each other. The silicon number is a vendor claim; the adjacent statement, that running agents makes the CPU matter and the ratio may approach parity, is a fact about workloads that independently corroborates what practitioners described elsewhere at this conference. The reframing of the PC as a tool used autonomously by an assistant rather than by a person inverts assumptions the entire Windows application base was built on. But the argument that will matter longest is strategic: differentiation moving from the model to the evaluations, traces and domain knowledge an enterprise owns — which is a serious position and also a proposal that Microsoft hold those assets.

Microsoft Build

Inference Stopped Being the Cheap Half
Inference Stopped Being the Cheap Half

The session builds on the observation that thinking models consume large numbers of tokens while reasoning, which means serving no longer resembles the profile that shaped serving infrastructure. Their account of where difficulty lives transfers past any hardware: the hard problems are memory management, scheduling and utilisation, not arithmetic — the chip does the arithmetic, and the surrounding system decides whether it is busy. The concrete bottleneck is key-value cache management as contexts lengthen and concurrency rises, with reuse rather than recomputation as the optimisation. The batching change is small to state and large in effect, because variable-length output stopped being an edge case and static batches are held hostage by their slowest member. The commercially decisive claim is that none of this requires rewriting the application layer, since gains behind an unchanged interface are adoptable by teams who never think about hardware.

Google I/O

A 128K Window Removes the Main Reason to Reach for a Hosted Model
A 128K Window Removes the Main Reason to Reach for a Hosted Model

The specification change that matters is the context window moving from 32,000 tokens to 128,000 for smaller models and up to 256,000 for larger ones, because it changes which problems are solvable without infrastructure. A 32,000-token limit means retrieval, chunking and index management; at 128,000 many tasks fit whole and the workarounds become unnecessary. The deployment range runs from a browser with zero ongoing server cost through local runtimes to one-click hosted endpoints, and the strategically significant detail is interface compatibility — a local model speaking the same protocol as hosted APIs is substitutable without changing application code, which makes placement an operational choice rather than an architectural commitment. That is what makes open weights competitive: not being better, but making switching free.

Google I/O

Jeff Dean on Why Tools, Not Models, Are the Next Bottleneck (Google I/O 2026)
Jeff Dean on Why Tools, Not Models, Are the Next Bottleneck (Google I/O 2026)

Four of Google's model, product and search leads on what changes once agents run for hours rather than seconds, and the most quotable argument comes from Dean: the constraint is moving out of the model and into the tools around it. By Amdahl's law, an agent spending half its time in tools built for human-speed interaction cannot gain more than a doubling however fast the model becomes — which reframes a great deal of current infrastructure work as latency debt. Their internal response is concrete: rewriting Python tooling into Go, framed as a fully specified translation task rather than an open prompt, produced order-of-magnitude speedups overnight. Reid supplies the counterweight from Search, where acceptable latency turns out to scale with how much work is being taken off the user rather than being a fixed budget. Woodward's detail is the quietest and perhaps the most telling: teams that have stopped writing product documents for humans and now write context files for models to act on directly.

Google I/O

Quantum's First Contribution to AI Is a Dataset, Not a Speed-Up
Quantum's First Contribution to AI Is a Dataset, Not a Speed-Up

The claim most likely to matter here is about data rather than computation. The measurements behind modern structural biology began accumulating in the 1970s and took roughly fifty years of painstaking work to become the database that made the protein-structure breakthrough possible — and a quantum computer could produce valuable training sets where collecting them experimentally is impractical. That inverts the usual framing, because a dataset does not need a fully error-corrected machine: it needs to be produced once, correctly, and then has permanent value. The technical status report is specific, with coherence times improved roughly tenfold and the remaining obstacles described as system-level engineering rather than physics. The most actionable statement concerns cryptography, where an algorithmic result rather than hardware progress moved the timeline inward.

Google I/O

Jensen Huang's GTC 2026 Keynote: Vera Rubin, the Groq Deal and the Inference Inflection
Jensen Huang's GTC 2026 Keynote: Vera Rubin, the Groq Deal and the Inference Inflection

Jensen Huang used NVIDIA's 2026 GTC keynote to argue that AI has crossed an inference inflection: models that once only generated text now reason and act, and each step multiplies the compute a single task consumes. He put NVIDIA's forward demand visibility above one trillion dollars through 2027, then spent much of the keynote explaining why that is a factory-economics claim rather than a chip claim — a gigawatt of AI factory costs roughly forty billion dollars before any compute is installed, so throughput per watt is what determines revenue. The technical centrepiece was the Vera Rubin platform; the strategic surprise was NVIDIA absorbing the Groq team to cover the low-latency decode that NVLink alone cannot reach. He closed on two extensions of the agentic thesis: OpenClaw as an emerging operating system for agents, hardened for enterprises as NemoClaw, and physical AI, where four new robotaxi partners add roughly eighteen million vehicles a year.

NVIDIA GTC

Traffic Rises, Revenue Per User Falls: The Chart Behind Every Telecom Strategy
Traffic Rises, Revenue Per User Falls: The Chart Behind Every Telecom Strategy

The chart defining this industry's problem is described in one line: traffic keeps rising while revenue per user steadily creeps down, which the speaker rightly calls the narrative for the sector. The adoption figure offered — a tenfold rise this year with a projection past half of users by 2030 — is real growth from a small base attached to a projection that assumes the curve continues through the part where adoption gets hard, which is where forecasts in this industry have historically failed. The observation about spectrum holdings shifting is easy to skip and shapes more than it appears, because spectrum is the one input that cannot be manufactured or competed into existence, which is why competitive analysis here differs from other technology sectors. The most useful moment is an aside about getting caught up in evolving networks, and the numbers above are why that instinct is correct.

MWC Barcelona

Satellite Stopped Competing With Terrestrial and Started Filling Its Gaps
Satellite Stopped Competing With Terrestrial and Started Filling Its Gaps

The number establishing how fast this changed is that around seventy per cent of the global telecommunications market now holds at least one non-terrestrial partnership, against a situation twelve months earlier where most operators with anything had exactly one. The framing offered is pragmatic partnership rather than competition, and the word choice does real work: satellite connectivity spent most of its history as a competing answer to the question terrestrial networks answered, and lost comprehensively on cost wherever people actually live. What changed is the question. The coverage gaps identified recur weekly or monthly and are heterogeneous — maritime, remote industrial, disaster response, rural — each with different latency tolerance and willingness to pay, which is why no single answer covers them and why the connected-device case is stronger than the consumer one.

MWC Barcelona

"The Problem Isn't a Bubble, It's Rationing": Davos on Financing the Buildout
"The Problem Isn't a Bubble, It's Rationing": Davos on Financing the Buildout

The session's organising claim is that the bubble conversation is a category error: for the next one to three years the binding problem is rationing capacity, not overbuilding. Friar supplies the strongest evidence anyone offered publicly this week — compute constraints delayed frontier models by six to eighteen months, which makes the shortage a fact about a roadmap rather than a claim about demand. Where the session is less useful is the critique it declines to engage. Asked about circular financing, Friar identifies the implication that demand is not real and rejects it, which answers the weakest version of the argument; the stronger one accepts that demand is real and observes what happens to a loop when the external funding sustaining it slows. Nobody tests it, which is unsurprising given that every participant sits inside the arrangement. The vocabulary — generational opportunity, a fast river you want your boat in — is the register of allocation, in which every answer arrives as a reason to move faster.

World Economic Forum Annual Meeting

A Strategy Built on Diffusion Rather Than the Frontier
A Strategy Built on Diffusion Rather Than the Frontier

The framing difference made explicit here is worth more than the numbers: the approach described concentrates on diffusion and does not talk about artificial general intelligence. That is strategic rather than rhetorical, because a programme organised around reaching a threshold prioritises frontier capability while one organised around diffusion prioritises getting existing capability into industries — different investment, metrics and definition of success. The operational emphasis follows: building scalable systems in production across many datasets, and lowering the cost of using AI through cloud-level optimisation. That is where diffusion and cost converge, since the marginal adopter is by definition more price-sensitive than the last one. Open weights fit the same pattern as distribution mechanism rather than philosophy. What the session avoids is what is given up, and the position is the opposite of the one taken by the frontier labs elsewhere at this conference.

World Economic Forum Annual Meeting

Huang's Five-Layer Cake: The Infrastructure Argument He Took to Davos
Huang's Five-Layer Cake: The Infrastructure Argument He Took to Davos

Huang brings a diagram to Davos: AI as a five-layer cake running energy, chips, cloud, models, applications — with economic benefit landing at the top and every layer below it a precondition. His argument for why this is a genuine platform shift rather than a product cycle is the strongest part, and it does not rest on his commercial position: software was pre-recorded and worked on structured data, whereas a machine that reasons about unstructured input and inferred intent makes previously impossible applications possible. What the framing accomplishes is worth noticing separately. By presenting the layers as a chain rather than a portfolio, it converts infrastructure spending from a bet into a prerequisite, and the question of proportion between layer-two spending and layer-five value stops being askable. Read against the GTC keynote two months later, the same business gets two framings: one a case for choosing his product, the other a case for the category existing at the scale he needs.

World Economic Forum Annual Meeting

Sovereignty Without the Servers: The Digital Embassy Idea at Davos
Sovereignty Without the Servers: The Digital Embassy Idea at Davos

The proposition is narrow and more consequential than it sounds: a country extends its critical digital infrastructure into another state's territory while retaining legal control over the data, compute and governance. The inversion starts from a physical fact — power and water cannot be relocated across borders, so move the facility to where they already exist rather than demanding they appear where the sovereignty is. The concept predates AI, having been arranged to protect continuity of essential government services, and the change is one of scale: a defensive instrument satisfied by modest infrastructure becomes a template for where the world's compute physically sits. The argument for standardising is practical rather than principled — bilateral agreements otherwise reinvent the same legal and technical answers, and investors want a tried framework in place before capital is committed. What it does not resolve is leverage, since the scenarios that make sovereignty matter are precisely the ones in which holding the buildings confers options.

World Economic Forum Annual Meeting

The Grid Might Just Get Bypassed: Davos on Powering the Compute Race
The Grid Might Just Get Bypassed: Davos on Powering the Compute Race

The panel is billed as an energy discussion and turns into an argument about who decides. Sridhar's observation is the one that carries: large refineries draw hundreds of megawatts and do not use the grid at all, generating on site because routing industrial demand through infrastructure built for everyone else never made sense — and upgrading that shared infrastructure for a single gigawatt-scale consumer is, in his word, bonkers. Around that sit the constraints that make it tempting. Grids in the United States and Europe are decades old, permitting runs to years even where it has been halved, and Busch's account of Sweden adding ten reactors' worth of unstorable wind capacity while consumption stayed flat is a precise illustration of why installed capacity is the wrong measure. Payne supplies the argument operators will use wherever power is scarce: AI infrastructure produces more economic output per electron than any other industry by an order of magnitude. Persuasive on its own terms, and about to be deployed in places where the competing use is a neighbourhood.

World Economic Forum Annual Meeting

Not Being Forced to Choose Between Hegemons and Hyperscalers
Not Being Forced to Choose Between Hegemons and Hyperscalers

The phrase worth extracting from this address is short: cooperating with like-minded democracies so as not to be forced to choose between hegemons and hyperscalers. It states compactly a problem most governments have not named, because the conventional framing of technology sovereignty concerns states, and this one puts corporate platforms in the same sentence as state powers. A country dependent on a small number of compute providers faces a structurally similar vulnerability that is rarely described that way. The proposed response is coalition rather than domestic substitution, which is realistic, since no middle power builds an alternative alone. The organising idea is variable geometry — different coalitions for different issues — and the most substantive claim links economic exposure to foreign policy directly: spreading trade and investment abroad is presented as the physical basis on which a state can afford to say what it thinks, since lowering how much a partner can hurt you is what makes a principled stand affordable.

World Economic Forum Annual Meeting

Twenty Small Risks Nobody Prices Together
Twenty Small Risks Nobody Prices Together

The most portable idea in this panel is probability reasoning rather than a forecast: twenty risks each carrying roughly a five per cent chance price in individually as almost nothing, while the odds that one of them occurs are considerably better. That explains the disconnect between chaotic headlines and equities near record highs, because markets price risks separately and nothing forces aggregation. The economic argument makes the same point from the other direction — growth holding steady at 3.3 per cent is not resilience but offsetting forces, with AI investment, a wealth effect and fiscal spending cancelling policy drag. The panel's genuine split is about time horizon rather than facts, and their admission about repeatedly wrong rate forecasts deserves weight when the same apparatus estimates AI's contribution to output. Their closing risk is organisational rather than financial.

World Economic Forum Annual Meeting

Two Banks Went Opposite Directions on Identity, and Both Worked
Two Banks Went Opposite Directions on Identity, and Both Worked

The framing statistic is organisational rather than technical: around eighty per cent of organisations expected to have platform engineering teams going into 2026, up from about forty-five per cent a couple of years earlier. The interesting part is the doubling. The problem described is teams solving the same problems separately, producing inconsistency and redundancy — dangerous not because of duplicated effort but because each independent solution has its own security properties, and the organisation's real posture is the weakest rather than the average. The most valuable content is that two financial services organisations went in diametrically opposite directions on workload identity and both are described as working, which implies the choice is determined by context rather than by a general answer. The honest note follows immediately: even with standardised patterns the result remains fragmented.

AWS re:Invent

A Correct Answer That Cost 1.3 Million Tokens
A Correct Answer That Cost 1.3 Million Tokens

The story that should outlive this session is about a question that worked perfectly and cost 1.3 million tokens. The answer was good, it passed the team's question-and-answer checks and acceptance testing, and the tool calls were sensible — yet a single query consumed enough to have destroyed throughput at production scale. That is a category of defect traditional software mostly does not have, because the cost is incurred inside a reasoning process with no fixed shape. The team extended their agent framework for per-turn reasoning visibility and then bounded how much data the agent could pull, a sequence that matters because the guardrail could not have been written before the behaviour was observed. Their architecture separates agent logic from data logic so each side scales independently, and their closing advice is to find the simplest pattern that delivers the benefit and analyse with real data afterwards.

AWS re:Invent

A Declared View Removes the Pipeline It Would Have Taken to Maintain It
A Declared View Removes the Pipeline It Would Have Taken to Maintain It

The change is easy to miss and large in practice: rather than configuring an extraction pipeline with triggers and scheduling, you declare a materialised view and the system maintains it. That collapses work most data teams treat as unavoidable, since a pipeline is a transformation plus the orchestration around it, and most of that orchestration exists to keep a derived dataset current. The performance argument comes with both a number and a mechanism, which is rarer than it should be — around twenty per cent reduced cost, driven by local disk, where exhaustion fails jobs and constraint slows them with stragglers holding up everything else. That contradicts where teams look first, since disk exhaustion presents as symptoms shared with many other problems. The most honest passage concerns engine upgrades, which got harder precisely because the data lake features teams want depend on the newest releases.

AWS re:Invent

The Root Key Has to Sit in Plain Text, and Everything Follows From That
The Root Key Has to Sit in Plain Text, and Everything Follows From That

Beer names the constraint that makes key management genuinely hard, and it is not the mathematics: the key at the top of a hierarchy must be in plain text at all times for the system to stay available. Everything below can be encrypted by something above; the root cannot, or there is nothing to start from. The threat model that has moved from theoretical to planning-relevant is harvest now, decrypt later — capture encrypted traffic today, decrypt it when capability arrives — which means the exposure is to everything transmitted now rather than to a future secret, and inverts the usual reasoning about when to migrate. The strategic argument is about delegation, and it is a vendor's argument that happens to be right: cryptographic agility is not something most organisations can retrofit, because the assumptions live in code written by people who have left. One remark connects the session to the rest of the conference, on certificate infrastructure built for a countable number of endpoints.

AWS re:Invent

What an Agent Actually Is: Marc Brooker on Agent Infrastructure (re:Invent 2025)
What an Agent Actually Is: Marc Brooker on Agent Infrastructure (re:Invent 2025)

Brooker builds the definition from the bottom up rather than asserting it, using a deliberately absurd arithmetic task to separate three categories: what a model computes reliably as a fixed function of its input, what merely needs to arrive in the system prompt, and what genuinely requires reaching into the world. Only the third category justifies a tool, and the distinction matters because most production disappointment comes from tools built for the first two. His working definition follows — a system given a goal that loops between inference and tool calls until it reaches one — with the observation that modern agents increasingly embed code in their definitions, not for expressiveness but because replacing inference steps with deterministic code improves reliability while lowering both latency and cost. The remainder covers what production actually demands around that loop: somewhere to run, memory that persists preferences, a gateway to internal and external tools, evaluation, and formal methods applied to policy.

AWS re:Invent

A Query Went From 30 Seconds to 46 Milliseconds. Resizing Would Not Have Helped
A Query Went From 30 Seconds to 46 Milliseconds. Resizing Would Not Have Helped

The framing question is better than the answer most teams give: can the problematic statement be identified and fixed, and separately, is this the right instance type. The order matters, because a database at full utilisation from poorly written statements presents identically to one that is genuinely undersized, and resizing is a one-line change while query analysis is work. The number that settles the argument is a query moving from thirty seconds to forty-six milliseconds — a factor no amount of hardware closes, which is why sizing is the wrong first move. Their treatment of caching depends entirely on sequence: applied before the query is understood it hides a problem that returns when access patterns shift, and applied afterwards it removes work that genuinely did not need repeating. The operational figure that makes the whole discipline affordable is a failover of up to thirty seconds, which turns instance sizing into a reversible decision.

AWS re:Invent

Trust Becomes a Key Policy
Trust Becomes a Key Policy

The session opens by dismantling the reassuring version of its own subject: you put a box around the workload, secure it, call it confidential computing, and the problem is solved — which is why the presentation exists. The gap comes down to one question: how do you know the code you are talking to is the code that is running, rather than taking someone's word for it. A protected environment addresses operator access but not the customer's actual objection, which is that they cannot confirm any of it. Attestation converts the claim into a signed measurement, and the step that turns evidence into a control is a key policy permitting operations only when the environment matches. Trust becomes arithmetic rather than process, with no reviewer to convince and no exception to grant, which is what allows a model owner and a data owner to collaborate without trusting each other.

AWS re:Invent

How to cite this page

Copy a stable citation for this source-backed profile.