Tokenmaxxing is the New "Lines of Code"
Nicholas Arcolano
- When
- Wednesday, July 11:30 PM – 1:50 PM · 20 min
- Where
- Leadership 2San Francisco, CA · imported from ai.engineer's public schedule feed
About this session
Somebody in your company is going to ask what you're getting for all that AI spend. If you don't have a good answer, someone else will make one up... and it might be "total tokens consumed". That's how tokenmaxxing becomes policy: not because anyone thinks it's a good metric, but because engineering didn't offer a better story. I work with datasets spanning hundreds of companies, hundreds of thousands of engineers, and billions of lines of shipped code to understand how AI engineering is evolving and what actually matters to measure. One thing I've learned is that raw token spend is a VERY crude estimator of value. For example, across levels of token spend, cost per merged pull request varies 300x — but output only varies 2x. The good news is the data also shows what DOES matter, and it's measurable and actionable – but most teams aren't tracking it yet. This talk will give you the data, metrics, and frameworks you need to keep your org from adopting the latest terrible vanity metric. You'll learn what actually separates teams that scale AI effectively from those just burning tokens, and how to tell the story that keeps your AI investment funded and growing.
Speaker
Head of AI & Research, Jellyfish
Head of AI & Research at Jellyfish, building AI agents and data platforms that help software engineering organizations measure and navigate AI transformation at scale. Leveraging massive real-world data sets to study what's working (and what's not) about AI tool and agent use across the industry, and sharing these learnings through published research and benchmarks so engineering leaders can make confident, evidence-based decisions. Harvard Ph.D., previously at TrueMotion (CMT), Runkeeper, MIT Lincoln Laboratory.
More in AI Architects: Tokenmaxxing
- The Z/L Continuum: Should AI Engineers Still Read Code?Wednesday, July 1 · 10:45 AM – 11:05 AM · Leadership 2
- Is Orchestration the Future?Wednesday, July 1 · 11:10 AM – 11:30 AM · Leadership 2
- How to Kill the Code ReviewWednesday, July 1 · 11:40 AM – 12:00 PM · Leadership 2
- The Death of the Code ReviewWednesday, July 1 · 12:05 PM – 12:25 PM · Leadership 2
- Engineering Agency out of the Happy PathWednesday, July 1 · 1:55 PM – 2:15 PM · Leadership 2
For developers: this programme is open data — JSON, iCal, schedule XML and an MCP endpoint.Show endpointsHide
- JSONEvery published session and speaker, in one request./aie-worldsfair-2026-import/feed.json
- iCalSubscribe in Google, Apple or Outlook Calendar./aie-worldsfair-2026-import/feed.ics
- Schedule XMLfrab / pentabarf — the format conference apps import./aie-worldsfair-2026-import/feed.xml
- MCP + RESTPoint Claude at the programme. OpenAPI 3.1 included./agents
No key, no signup, CORS open. Everything here is generated from the same data the organisers edit.