Better with Kent

Kent C. Dodds

Solo episodes from Kent C. Dodds on durable skills for people who ship software: judgment, accountability, problem clarity, and what stays valuable as AI takes on more implementation. Kent teaches directly on camera — no guest, one idea at a time. Complements guest interviews on Become a Product Engineer (Chats with Kent). Episode 1 adapts The Last Software Engineer; later episodes cover traps like building the wrong thing faster and skills like making user pain visible. Subscribe for evergreen episodes as the series grows.

Puntate

  1. How to Prioritize Software Tasks

    13 h fa

    How to Prioritize Software Tasks

    Kent walks the Kano model on a real food-delivery backlog: Must-be, Performance, and Delighter — why GPS was a wow in 2015 and a basic today, and why you cannot delight your way out of broken basics. Chapters 0:00 The backlog fight1:39 What type of feature is this?2:15 Basics (Must-be)3:47 Performance needs5:38 Delighters6:32 GPS lifecycle reveal7:56 Why silence misleads teams10:00 Cannot delight out of broken basics10:36 AI and the junk drawer11:52 Prioritized build order14:25 Homework and close Better with Kent — Durable skills for people who ship software. You have five backlog items and everyone wants their feature first. Kent uses a food delivery app example and the Kano model (Must-be, Performance, Delighter) to show what type each feature is — and what to build first. Land three beats: broken confirmation email is a Must-be (fix before anything else), estimated delivery accuracy is Performance (more accurate = more satisfied), surprise discounts and group ordering are Delighters (fun to build, dangerous when basics are broken). The GPS reveal: tracking felt like magic in 2015; today missing GPS means users leave. Why teams get this wrong: silence in support is not proof basics work — most users leave without filing tickets. You cannot delight yourself out of broken basics. AI makes it worse when agents churn exciting Delighters while hygiene features rot. Homework: label five real backlog items, fix broken basics first, ask whether last year's Delighter became today's Must-be. Become an Epic Product Engineer guests cited: Wayne Allan, Sean Roberts, Swizec Teller, Don Norman, Dillon Mulroy, Dax Raad. Links Watch on YouTube

    16 min
  2. What Software Engineers Need in 2026

    5 gg fa

    What Software Engineers Need in 2026

    Kent maps the durable skills that stay valuable as agents take more implementation: clarity, judgment, empathy, feedback loops, systems thinking, agent fluency, and ownership — with practical homework for each cluster. (00:00) - Intro: Google stat and durable skills (00:20) - Why now (01:08) - Durable skills map (01:25) - Clarity & judgment (03:40) - Wayne Allan: build the right thing first (04:28) - Practice: clarity & judgment (06:01) - User empathy & feedback (07:29) - Practice: empathy & feedback (08:56) - Systems thinking (12:22) - InfoWorld: AI coders need good engineers (18:52) - Agent fluency (20:14) - Practice: agent fluency (21:26) - Ownership (23:03) - Slow down on purpose (27:05) - What to deprioritize (28:04) - Homework Better with Kent — Durable skills for people who ship software. Episode 1 is the map. Agents can implement faster every month; the expensive mistake is building the wrong thing even faster. Kent walks through seven skills that were valuable decades ago and still matter in 2026: problem clarity, domain depth, judgment, empathy, feedback loops, systems thinking (including closing the agent loop), agent fluency, and ownership. Three clusters pair each skill area with concrete practice — stakeholder rooms, wiring daily feedback, building tests and CI so agents can iterate. Kent cites Become an Epic Product Engineer guests (Wayne Allan, Jack Ryan, Aaron Francis, Dillon Mulroy, Swizec Teller, Ruben Casas, and others), reacts to Matt Asay's InfoWorld piece on AI-generated code, and closes with homework you can do this week. Not a tool demo. Not a PM course. Not a framework checklist — just durable skills for people who ship software. Subscribe and comment with topics you want covered. Chats with Kent (Become an Epic Product Engineer) continues with guest interviews; Better with Kent is Kent thinking out loud on camera. Links InfoWorld — AI coders need good software engineers (Matt Asay)The Last Software Engineer (essay)Become an Epic Product Engineer (guest podcast)Better with Kent on kentcdodds.com

    30 min

Descrizione

Solo episodes from Kent C. Dodds on durable skills for people who ship software: judgment, accountability, problem clarity, and what stays valuable as AI takes on more implementation. Kent teaches directly on camera — no guest, one idea at a time. Complements guest interviews on Become a Product Engineer (Chats with Kent). Episode 1 adapts The Last Software Engineer; later episodes cover traps like building the wrong thing faster and skills like making user pain visible. Subscribe for evergreen episodes as the series grows.

Potrebbero piacerti anche…