AI and Work

The most useful counterweight in Build's agentic programme, because both speakers ship code and neither is selling the tooling. Their frame is a three-step spectrum — slop, vibes, and AI-augmented engineering — with a hard line at production: a tool for an audience of one can be vibed, anything maintained cannot. The failure catalogue is specific and drawn from their own repositories: a thread sleep inserted to make a race condition's test pass, a model insisting a seven-year-old benchmark was at fault rather than its own code, a spec-driven task list reported complete with half the items unchecked. Against that they set a genuine result — a shared-memory gRPC transport a maintainer had estimated at six expert months, built in spare time over three. The distinction they draw is sculpting rather than prompting. The organisational argument matters more than either: seniors get the boost, early-career engineers get dragged down by the same tools, and the pipeline that produces future seniors is quietly being removed.

Microsoft Build

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

The finding that contradicts how most teams deploy AI assistance is stated almost in passing: the tenfold return arrives where an engineer is weakest rather than strongest, so someone without a security background suddenly shows a better security posture. That reverses the usual rollout order, which gives these tools to the strongest engineers first on the theory that leverage compounds on capability. It also creates a verification problem, because the reviewer most likely to be assigned shares the same gap. The speaker who previously ran the foundation behind Kubernetes brings a specific scepticism about lock-in, framed as this era already reproducing the last one's portability and cost-control problems — though the sharper observation is that context held in implicit memory or a conversation window has no export format at all. Their overnight scheduler blocks only for architectural decisions, which is a well-drawn line with no one watching it.

Microsoft Build

The most useful sentence across this hour answers whether you watch what the model is doing: it depends on the stakes. A small interface prototype gets no supervision; code running a sandbox inside his own system got close attention and a series of attempts to break it. That is a better review policy than most organisations have written down, because when generation becomes cheap, review is the scarce resource and spending it uniformly under-reviews the dangerous code. The observation that reframes the economics is that a hard problem means the model works for ten minutes while you do something else, so difficult tasks have become the cheaper ones in attention — inverting a relationship that has held for the entire history of software. The remark about trusting his own software after four months of use, rather than because an expert wrote it, is a real shift in what evidence counts.

Microsoft Build

The observation that organises this session is not about capability but about attention. Engineers increasingly file a ticket rather than opening an editor, and the code comes back — which changes what the surrounding tools are for. If the agent works while you do something else, the conversation between you is no longer a workspace; it is the mechanism by which the agent surfaces a question it cannot resolve alone. Interfaces built for continuous conversation optimise for flow, and interfaces built for interruption should optimise for the opposite. A runtime constraint follows immediately: an agent that starts a long-running job cannot block until it finishes, which turns out to be a workflow-engine problem rather than a model one. The panel's closing formulation — that deciding what to build is the hard skill and always was — reads as reassurance and functions as a warning, since that judgement is downstream of exactly the work now being delegated.

Google I/O

Four months after Davos, Hassabis put a sharper number on the same forecast: AGI around 2030, give or take a year, arriving gradually rather than as a single moment. His test for it is concrete — a model with a 1901 knowledge cutoff that could produce Einstein's 1905 insights — and by that standard current systems plainly fail. The interview is more useful than the Davos panel on two fronts. First, competitive position: he argues Google's advantage is being the only organisation holding the full stack from chips to billion-user products, citing 900 million monthly users on the Gemini app. Second, method: the AlphaFold story of choosing to fold every known protein at once rather than run a request service is his working example of what acceleration should look like. He closes on a warning aimed at the Bay Area — that direction matters more than velocity, and that the current frenetic pace is not conducive to the deep work the next advances require.

Google I/O

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

The framing figure should appear in more discussions of AI adoption: in the markets under consideration fewer than twenty per cent of people are using AI at all, with benefit concentrated in developed markets. Every debate about economic impact assumes access, and this session concerns the four-fifths for whom the question has not arisen. Digital literacy is named as the representative constraint, and it matters more than infrastructure because the sequence has already run once — mobile reached these markets faster than forecast, and those who missed out were not the uncovered but those who could not use what coverage delivered. The technical description is a distribution argument rather than a product one, and depends on the layers above being built by people with local knowledge, which the same conditions suppress. The operational discipline is what makes it credible: segmented retention reviewed every week or two, because aggregates rise while intended beneficiaries leave.

MWC Barcelona

The most useful sentence is a diagnosis of how clients are getting it wrong: they see a cost opportunity rather than a revenue one. That framing decides everything downstream, because an organisation treating AI as cost reduction measures success by what disappears and arrives at a smaller version of what it already was. The market number offered — seventeen per cent index growth in 2025 that nobody foresaw — is deployed against bubble anxiety and argues in both directions, since unforecast gains are poor evidence for confidence in any current consensus. The panel then locates the real source of instability outside technology entirely, in three geopolitical situations generating enough uncertainty to dominate planning, which is a corrective worth taking seriously at a technology conference. Their closing question about thriving across multiple futures is correct and sits uneasily beside the cost framing they diagnosed at the start.

World Economic Forum Annual Meeting

The distinction in this session that deserves to travel is a two-word change: the model is moving from an attention economy to an attachment economy. That changes what is measured and what regulation would have to address, because attention competes for time while attachment competes for relationship, and the two produce different products from identical technology. Attention is finite in a way people notice; attachment produces reliance that feels like preference, which makes it harder to regulate for the same reason it is harder to notice. The supporting argument is about incentives rather than intent: earlier engagement produces more data and longer relationships. The regulatory proposal — measuring well-being outcomes rather than asking for safety by design — identifies the right target without solving the measurement problem that made regulators settle for a floor in the first place.

World Economic Forum Annual Meeting

The most consequential thing said here is not about technology: the only route out of the deficit position is a productivity boom, and without one the consequences of that spending worsen. That makes the AI question load-bearing in a way most discussions of it are not. The historical parallel offered — the computer revolution visible everywhere except in the productivity statistics — cuts both ways, because the gap before those gains materialised was well over a decade. The evidence for optimism is a 2.8 times return in bounded proof cases, immediately qualified by the observation that enterprise-scale adoption requires spreading the technology across every function and will take time. The distance between those two statements is the whole adoption problem, and nobody supplies the number the fiscal argument depends on. The panel's observation that much of the industrial base sits in Asia is a significant qualification to an argument about exceptionalism.

World Economic Forum Annual Meeting

The fact that makes this session difficult is not that the scam compounds are hidden but that they are known. International law enforcement knows their street addresses, because hundreds of survivors have said so and digital traces corroborate it — four or five hundred facilities across three countries that stole between 50 and 85 billion dollars in a single year. This is not a detection problem. The strongest argument made is that the captive workforce is the operation's weakest link rather than merely its cruellest feature, because thousands escape and can describe who is doing this, where and how. The proposed lever is deliberately modest: international physical inspection of five or six facilities rather than all of them. The structural diagnosis is about tempo, and synthetic media widens the asymmetry further.

World Economic Forum Annual Meeting

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

The sentence founders should sit with concerns cost structure: a technology this disruptive inverts the build-versus-buy calculation companies make. For thirty years that calculation was stable, and software companies existed in the gap between what a customer needed and what they could justify building. The concrete example is more useful than the abstraction — an interaction costing ten dollars means you could not afford the customer experience you wanted, which describes a category of product that was economically impossible rather than merely underserved. The observation with the widest implications is that operating in English addresses roughly ten per cent of the world, paired with the harder question of whether these systems handle a three-hour conversation. The analogy that does not hold is the internet, which created distribution where none existed rather than changing the cost of things already done.

World Economic Forum Annual Meeting

A show of hands opens the session: nearly everyone has piloted, far fewer have scaled, and everyone who scaled hit problems they did not anticipate. What makes the panel useful is where the four answers do not point. None of the executives — running a healthcare manufacturer, a payments network, an energy producer and a consultancy — blames model capability, cost or data infrastructure. All four describe an organisational constraint. McInerney's account is the sharpest and is an account of failure: eighteen months of executive advocacy and democratised model access produced nothing, until three hundred senior leaders were put in a room for two days and made to build agents themselves. Jakobs supplies the mechanism worth copying, measuring returned clinician time against the three to seven minutes a patient currently receives rather than against cost. Nasser rejects the premise that acquiring compute produces value, and locates returns in operations rather than in the back-office functions most organisations automate first.

World Economic Forum Annual Meeting

A year after their first joint appearance, the heads of Anthropic and Google DeepMind returned to a shared stage and disagreed mainly about speed. Amodei held to a horizon of one to two years for systems that outperform humans across most cognitive work, resting the claim on a self-improvement loop that runs through code; Hassabis kept to the end of the decade, arguing that verifiable domains like coding and mathematics automate far earlier than natural science, and that the capacity to pose a new question rather than answer an existing one is still missing. The exchange is most useful where they converge: both accept the loop is the variable that decides everything, both are sceptical of doomerism without dismissing the risk, and both want more time than the competitive dynamic allows. Amodei's chip-export argument and Hassabis's call for minimum international safety standards are the two concrete policy asks.

World Economic Forum Annual Meeting

The decision that changed the audience was to stop restricting access and invite the creators already working on social platforms in. The resulting figure is the one worth keeping: eighty per cent of the audience reached had never subscribed to the organisation's own channel. Most content metrics measure how well you serve people who already found you; this measures the opposite, which is much harder to move. The mechanism is a distribution decision rather than a production one — they did not make content for a new audience, they let people who already had that audience make it. Underneath sits a genuine format constraint: golf is hard to see, and the traditional broadcast grammar struggles with a ball travelling three hundred yards against sky across a course spanning miles. Creators were not out-producing the broadcast; they were solving legibility, which is why the falling cost of production matters more here than elsewhere.

AWS re:Invent

Drawn from a year of engagements with more than a hundred companies, this is the most direct challenge in the season's programme to the assumption that faster code generation produces faster delivery. Mishra and Raja open with external evidence rather than their own: an industry study putting realised velocity gains in the ten to fifteen per cent range, and a controlled experiment in which developers using AI estimated themselves roughly a fifth more productive while measurement showed them a fifth slower. Their diagnosis is that both prevailing working styles fail for opposite reasons. Handing an ambiguous problem to an agent and awaiting a finished result produces a volume of code the developer must nonetheless sign for and cannot confidently review, so it stalls before production. The senior engineer's alternative — decomposing the work personally and inserting AI into narrow slots — keeps the intellectual load exactly where it was, and leaves the surrounding process untouched, so hours saved in editing are consumed by the meetings that process still requires.

AWS re:Invent

The example that makes this session concrete comes from medicine: a nurse who sees a physician about to administer the wrong medication and, in an environment where speaking up carries risk, does not. Nothing about the nurse's competence was the failure — the information existed in the room and did not move. Security work makes this worse, because the cost of a missed signal is delayed and the person who spots it is often junior to the person who would be contradicted. The anxiety zone described — real pressure to deliver with no safety to contribute — is a fair description of an organisation during an incident, which is exactly when information most needs to travel. The four-stage model localises the failure so a leader can tell which intervention is needed, and the reframing of reversible decisions separates mistakes that deserve a penalty from those that do not.

AWS re:Invent

The most concrete attempt this conference season to answer a question the agentic coding sessions mostly leave open: if commit counts and hours saved are the wrong measures, what replaces them? Otto's account is unusually specific about why the obvious alternative fails — summing the small time savings a platform team delivers produces figures exceeding a hundred per cent of a developer's time, and a minute returned is not code in production. Their replacement borrows from Amazon's retail supply chain, where cost to serve measures what it takes to place a package on a doorstep, and applies the same shape to software: total cost divided by units of delivery, with the unit chosen to fit the team. The supporting research is the more quotable finding — across tens of thousands of developers over five years, individual velocity reverts to the team's mean, making team velocity the strongest predictor of both individual output and perceived productivity, which is the empirical case against measuring individuals at all.

AWS re:Invent