{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Travel Tech Podcast","title":"Code Is Twenty Percent of the Thing","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/f93ffd54\"></iframe>","width":"100%","height":180,"duration":744,"description":"AI made writing code nearly free, which only matters if code was ever most of the job.\nIn 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.\nWhat You'll Learn\nThe 20/80 split: Code is roughly 20% of a complex travel system, and the remaining 80% is knowledge of how the business actually works.\nVibe 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.\nEdge case cost: One modest custom fields feature at Zoftify took about five days of internal and client discussion before it was ready to build.\nFailure at the seams: Complex systems break at their interfaces and edge cases, not on the happy paths that teams test and load test.\nNo standard day: In airline operations, disruption from weather, aircraft swaps, or system faults is the normal state rather than the exception.\nExpertise outside the code: International fare specialists routinely beat GDS pricing engines by thousands of dollars by knowing where to break a fare.\nWhere value moves: As development costs approach zero, advantage shifts to network effects, knowledge of customer pain, and position in the customer journey.\nThe new job: When execution is cheap, deciding what to build and why becomes the core work for every team, not just well funded ones.\nTime-Stamped Highlights \n(0:00) One number about what software actually is\n(1:08) \"Why can't we just vibe code this?\"...","thumbnail_url":"https://img.transistorcdn.com/LxpvuNpWwfSGFL1KA1WhoZf9L55ykAqb5rgjXNFqi3c/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9mY2Yz/ZjA5OGE1ZmEyMTk4/ODJkYmU1YjhlYjRk/YTMzNC5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}