
Show Notes
AI is making knowledge work faster — but it’s also surfacing an uncomfortable tension: when the “doing” becomes cheap, the limiting factor shifts to everything humans do around it. This tension shows up in two places at once: inside engineering teams (identity, craft, and maintainability) and inside go-to-market (trust, distribution, and buying behavior). In this episode, Ian Painter, Oliver Deakin, and Adrian McKenzie approach this from lived experience rather than speculation. They have built and scaled data-intensive travel technology, operated deep inside enterprise environments, and navigated acquisition into a public-market business. Instead of defaulting to debates about job loss, they focus on a more operational problem: when building no longer creates advantage on its own, what does?
What You’ll Learn Why speed shifts the bottleneck rather than removing it: As AI compresses build cycles, advantage moves from execution to decision-making, positioning, and trust. How identity shapes resistance to AI tools: Engineers most attached to craft and code quality often struggle more than those focused on outcomes. Why “good enough” AI output is still valuable: Treating AI like a junior teammate reframes imperfection as leverage rather than failure. Where maintainability breaks in mixed human-AI teams: Code that functions can still create long-term friction when humans need to read, test, and evolve it. How startup time-to-market dynamics are collapsing: Mockups, demos, and customer conversations now happen days into company formation. Why distribution may matter more than differentiation: When demos converge, embedded relationships and brand trust regain power. How build-versus-buy decisions may flip: Internal teams coordinating many agents could replace procurement with custom internal builds. Why data becomes the defensible asset again: As software commoditizes, curated, hard-earned datasets grow in relative value. What near-term “seniority” may look like: Capability may increasingly be measured by how many agents someone can effectively coordinate. How to prepare students for knowledge work amid AI: First-principles thinking, critical evaluation, and tool fluency matter more than any single technology.
Time-Stamped Highlights (00:32) AI, Jevons Paradox, and the Framing Question (01:37) AI Acceleration in Knowledge Work (02:19) Ian Painter’s Founder Perspective (03:19) Oliver Deakin on Modern Engineering Practice (03:42) Adrian McKenzie on Leadership and Teams (05:24) Engineers’ Emotional Responses to AI (07:05) Why Imperfect AI Gets Dismissed (08:26) Hands-On Experience With AI Coding Tools (09:51) Functional Code Versus Maintainable Systems (11:26) Startup Dynamics in an AI-Accelerated World (13:07) Speed to Market and Competitive Compression (15:05) Sales, Marketing, and Distribution Shifts (19:42) Humans as the Limiting Factor (22:00) Brand Trust and Embedded Distribution (35:03) Data as the Enduring Moat (42:15) Advice for Future Knowledge Workers
Guests Ian Painter — Startup Advisor and Mentor. Previously, Vice President, Platform and Data at Cirium; Founder, Snowflake Software Ian is a seasoned technology leader in aviation data and analytics. He founded Snowflake Software in 2001, building enterprise data exchange and aviation data platforms that were later acquired by Cirium (RELX plc). As VP of Platform and Data, he oversaw data strategy and large-scale platform initiatives at one of the world’s most trusted aviation analytics companies. LinkedIn: https://www.linkedin.com/in/ianpainter/ Oliver Deakin — Fractional CTO, Advisor and previously Technology Leader at Cirium, Former Snowflake Software CTO, and Senior Engineer at IBM Oliver has served in senior technical leadership roles, including as CTO at Snowflake Software during its rise in aviation data solutions. He has deep practical experience with software architecture, developer tooling, and emerging technologies applied to complex domains like travel and real
More from Travel Tech Podcast
An AI asked to protect every passenger connection gave a flawless answer: cancel the flights. Kevin Hightower is Chief Innovation Officer at Cirium, where he leads Propulsion Labs, the company’s innovation group. He and host Alex Brooker, former colleagues at Cirium, discuss Kevin’s path from oceanic air traffic control at Lockheed Martin to Google’s drone delivery program, how AI is changing product development and decision making in aviation, Cirium’s aviation knowledge graph, and the data interoperability problems holding the industry back. What You’ll Learn Automating the routine: Lockheed’s oceanic ATC system let controllers comfortably manage 30 aircraft instead of a busy 7 to 15 by automating conformance checks and altitude probes. The three hour rule: No decision, from buying a car to buying a company, should need more than three hours of actual thought, with data gathering kept separate from thinking. Disposable prototypes: When AI cuts build time from months to days, the discipline shifts to throwing work away instead of defending ideas because of the effort already spent. AI as an accelerant for learning: Early career engineers who use AI to compress years of learning will outpace those who use it only to do an old job faster. Decisions, not dashboards: Most aviation decisions run roughly eight steps, and AI can now carry four or five of them before a human makes the call. The aviation knowledge graph: Aviation data starts with an aircraft and links orders, lessors, schedules, and tail swaps, so connecting it unlocks analysis no single dataset can. Efficiency before safety: AI will speed up flow management and sequencing well before it touches the safety critical systems that keep aircraft separated. The interoperability gap: Multi year, multi million dollar data lake programs rarely deliver usable value, and the real problem is combining data across boundaries while keeping control of it. Time-Stamped Highlights (0:00) Cold open: the AI that cancelled the flights (2:04) A Cessna ride to Embry-Riddle (4:48) "Do you want to kill people or save people?" Choosing air traffic control (6:26) Replacing paper strips over the Pacific (9:17) From Lockheed CTO to a quarter million drone deliveries (13:10) Why there's no one right way to be a product manager (16:22) The three hour decision rule (22:03) Formal testing in five minutes, not a few months (24:42) Fail fast, then fly everyone to Hawaii (32:39) Powering every decision connected to aviation (34:40) Behind the dip: analyzing every turn instead of one (47:17) Why nobody can predict the Charlotte arrival sequence (48:36) Could AI make travel worse for passengers? (54:09) Data interoperability and the $10 million data lake
AI made writing code nearly free, which only matters if code was ever most of the job. In this compilation episode, host Alex Brooker pulls together clips from seven past guests across travel software, airspace infrastructure, airline operations, corporate travel, content, and airline ancillaries who each arrived at the same idea independently. Alex Ragin of Zoftify puts a number on it: code is about 20% of a software product, and the other 80% is domain knowledge, process, and judgment. The episode follows that 80% through edge cases, daily operational disruption, fare construction expertise, and the question of what a product team's job becomes when execution costs almost nothing. What You'll Learn The 20/80 split: Code is roughly 20% of a complex travel system, and the remaining 80% is knowledge of how the business actually works. Vibe coding limits: A simple invoicing app can be vibe coded, but a CRM, ERP, or GDS cannot, because the hard part is specifying behavior rather than writing it. Edge case cost: One modest custom fields feature at Zoftify took about five days of internal and client discussion before it was ready to build. Failure at the seams: Complex systems break at their interfaces and edge cases, not on the happy paths that teams test and load test. No standard day: In airline operations, disruption from weather, aircraft swaps, or system faults is the normal state rather than the exception. Expertise outside the code: International fare specialists routinely beat GDS pricing engines by thousands of dollars by knowing where to break a fare. Where value moves: As development costs approach zero, advantage shifts to network effects, knowledge of customer pain, and position in the customer journey. The new job: When execution is cheap, deciding what to build and why becomes the core work for every team, not just well funded ones.
Two euros can decide who wins a metasearch sale. Inside most airlines, moving them is still revenue management's call, and it is rarely fast.
Everyone is racing to build the AI agent that books your trip, and nobody is building the thing that makes it safe to use one.
A guy who used to hand carry passports to airport cargo terminals just built the database he couldn't afford in 2018 for a fraction of the cost, and every application still passes through a human before it goes anywhere. Rob Lee is CEO and co-founder of Swift Passport and Visa Services, a company he started in 2008 helping private aviation clients navigate passport and visa logistics. In this conversation, Rob traces the industry from same day passport courier runs through the shift to eVisas and ETAs, and explains why his team uses AI heavily to build internal tooling while keeping customer data out of public AI tools and a human check on every application.