Curiosity, UX, and durable engineering skills with Annie Sexton

Kent talks with Annie Sexton, developer educator at ngrok, about the durable skills engineers need as AI changes the shape of software work.They cover how to teach complex technical ideas without assuming too much, why curiosity keeps engineers from becoming button pushers, how pacing and storytelling make educational content work, and why UX and product judgment are becoming harder to ignore.(00:00) - Meet Annie Sexton (02:15) - Teaching for the mid-level developer (05:48) - Jobs to be done for technical education (08:19) - Which fundamentals still matter with AI? (12:13) - Tricking people into learning (18:27) - Measuring educational content (23:13) - Pacing, hooks, and retention (30:12) - Education as trust-building (35:23) - Curiosity and engineering joy in the AI era (40:11) - UX as a differentiator (43:40) - Homework: make users awesome and audit a product Annie Sexton is a developer educator, software engineer, and technical video creator whose work has focused on making difficult infrastructure and software concepts feel approachable. In this conversation, she and Kent talk about teaching developers in an AI-heavy world, where syntax and implementation details are cheaper but curiosity, taste, pacing, and user empathy matter more.A major thread in the episode is education as product work. Annie describes writing for the mid-level JavaScript developer, using curiosity to pull people into topics they did not expect to care about, and treating comments, retention, and repeated confusion as feedback loops. Kent connects that to jobs to be done, teaching with agents enabled, and the need to understand what learners actually need now instead of preserving old rituals just because they were once necessary.They also dig into the emotional and practical shift AI has created for engineers. Annie talks honestly about losing some of the old joy of hands-on coding while finding a new place for that energy in product thinking, UX, and education. The episode closes with two concrete pieces of homework: read Badass: Making Users Awesome, and practice noticing every little point of friction in a product you almost chose but did not.HomeworkRead Badass: Making Users Awesome by Kathy Sierra and pay attention to the shift from making an impressive product to making users feel capable.Pick a product you considered using but rejected, then go through its onboarding or core flow again.Write down every specific point of friction, confusion, hidden error, awkward field, or moment where your eyes glaze over.ResourcesAnnie SextonngrokFly.ioBadass: Making Users AwesomeWebcomic StudioGuest: Annie SextonCompany: ngrokGitHub: @anniebabannieHost: Kent C. DoddsWebsite: kentcdodds.com𝕏: @kentcdoddsGitHub: @kentcdoddsYouTube: kentcdodds-plusPodcast: epicproduct.engineerSee on Epic Product Engineer