Sheamus McGovern founded ODSC roughly twelve years ago and now splits his time between the conference business and a role as venture partner and Head of AI at Cortical Ventures. His book, The AI Skill Flip, came out of a pattern he kept hitting: data scientists and software engineers coming to him asking whether AI was going to take their jobs and what they should do about it. He wanted to write something that sat between the doom narrative and the utopian one, both of which he thinks are wrong. The "flip" in the title is the observation that the balance of skills has shifted rather than disappeared. Five years ago a software engineer spent most of their time writing raw code. Now much of that time goes to judging and evaluating what the model produced and thinking further up the stack. The same flip applies in marketing, where the skill becomes knowing what good looks like and what persona you're targeting rather than producing the asset yourself. Asked what separates people who get real value from AI from people who don't, Sheamus lands on three things. First is passion, the plain will to get a good outcome, which he compares to what separates a strong startup founder from an average one. Second is creativity, which he argues AI increases rather than eliminates, because models are sycophantic and will happily build exactly what you asked for. His example is watching people reach for Replit, Base44, or Lovable and build a dashboard, when the real question is whether a dashboard is even the right artifact in a world of agentic workflows. Dan pushes the point further, noting that dashboards existed because software was expensive to build, so you built one thing and maintained it. Third is judgment. AI is excellent at producing output and terrible at judging its value, which Sheamus frames as another instance of the automation paradox. On whether judgment can be taught, Sheamus starts at the engineering level with evaluations. Traditional numeric metrics still apply, but open-ended evaluation is the hard part, and he watched engineers struggle with it while building his first RAG and QA systems. His QA team's honest response was that the system was generating text all the time and they had no idea how to test it. Above the engineering layer, judgment comes down to domain expertise and knowing what good looks like. He tells a story about generating a thirty-page contract with Claude Code, sending it to his lawyer for a quick review, and getting billed ten hours anyway, because the lawyer still had to read every word and apply their own judgment. The other half of teaching judgment is teaching people how AI actually works, so they neither trust it completely nor dismiss it. Once you see it as sophisticated pattern recognition rather than magic, the failure modes become predictable. It works well on established APIs and badly on new libraries. He'd asked Perplexity that morning for the top twenty personal AI frameworks and got Gemini and other Google products instead of OpenClaw and the other recent entrants. Dan asks whether prompt design still matters now that agentic loops can ask their own clarifying questions, and both agree the vocabulary has moved faster than the practice. People stopped talking about context engineering and started talking about the harness, but skills and memory are still context engineering wearing different clothes. Sheamus's view is that prompt engineering, context engineering, and skills are all the same underlying muscle, and the people who learned the first are quick at the third. Most teams are still doing a poor job of it, partly because the models are good enough to paper over sloppy input and hand back generic, unoptimized, expensive results. He describes users bouncing from the $20 plan to the $100 plan and still running out of tokens with no idea where they went. The deeper problem, and the one he spends a chapter on, is that knowledge work is both open-ended and unstructured. You get stuck debugging, a five-minute task becomes two hours, and workflows you assumed were deterministic turn out not to be. His own research pipeline pulling papers from Google Scholar and arXiv keeps hitting that wall, because author institutions appear below the names on one paper, on the left-hand side of another, and not at all on a third. His own use of AI changed substantially over the two and a half years he spent writing the book, which included interviews with about thirty people. The first version of Cortical's VC sourcing pipeline was hand-architected, with AI slotted into specific stages, ChatGPT or Claude to read reports and Perplexity to search. Now a single agent with the right skills and system prompts can do the whole thing end to end. He runs a personal assistant built from Claude Code and a bit of Codex that pulls attachments from his Google Calendar, cross-references his CRM and the Crunchbase API, and prepares the monthly list of two hundred startups he has to review. What used to be three hours of review is now thirty minutes of review plus a couple of hours improving the skills, which he readily admits is not obviously a time saving yet. He's also building a speaker CRM for ODSC, which has around eight thousand speakers in its database and about a thousand submissions per conference, using planning mode and Replit, sometimes adding features live during the meeting where they're requested. That leads to the conversation's real tension. Sheamus calls it the AI credit card, and warns that AI technical debt is piling up fast. He is emphatic that this means more engineers, not fewer, ranting about a post he'd seen that morning claiming software engineering wouldn't exist as a role by 2027. If you can produce code at 10x or 100x, someone has to evaluate, judge, and maintain all of it. Dan agrees on maintenance being the dominant cost but presses on a different point: not every piece of software is worth owning. Sheamus pushes back and they agree to disagree. His counterargument is that the gatekeepers on software development are gone, and the spreadsheet, still the most-used application in most companies, is going to be replaced by generated software and generative UI, interfaces that appear when you ask for them and get thrown away afterward. Dan draws the line at company size, where a startup should build and a large company already paying for tools has to weigh marginal value against maintenance cost. On junior engineers, Sheamus introduces the idea of cognitive debt alongside technical debt. Every task you offload, you also stop practicing, and he offers himself as evidence that his Python is worse than it was two years ago. His advice to juniors is uncompromising: learn the classical skills anyway, including how languages handle memory and which libraries matter, because that's what makes you good at reading and judging generated code. Then learn how AI works on top of that, which he thinks makes juniors potentially more employable than mid-level engineers because they can be AI-native from the start. He's also more hopeful than most about the junior hiring market, attributing much of the slowdown to pandemic over-hiring and, per a study he'd read, possibly to remote work leaving nobody in the office to train new staff. He closes on what he wants from companies, which is real training rather than buying a tool and declaring victory. His model is a matrix: universal skills like prompt engineering, governance, risk assessment, and evaluation across the top, then domain-specific practice underneath. He also makes a pitch for data literacy, having watched software engineers stare at a loss function or an R-squared with no idea what to do with it. Full episode notes
