Become an Epic Product Engineer
Introducing Become an Epic Product Engineer
This episode isn’t summarized yet
Create a free account and summarize it. In a few minutes you’ll have the key takeaways and a section-by-section summary.
Show notes
Kent opens Become an Epic Product Engineer: why product engineering is the durable skill as AI takes on more implementation, what to expect from guest conversations and homework, and where to start in the catalog.
- (00:00) - Introducing Become an Epic Product Engineer
- (00:38) - The archer metaphor
- (00:52) - Knowing what to build
- (01:05) - Learning out loud with guests
- (01:18) - Product engineers vs product managers
- (01:35) - Homework on every episode
- (01:55) - Episode highlights
- (02:15) - Better with Kent companion series
- (02:30) - Homework: subscribe and pick an episode
Software keeps changing, and AI is accelerating something that was already true: implementation is getting cheaper while knowing what to build matters more.
In this intro Kent frames the show - learning out loud with people who blend technical depth and product judgment - and why developers need product thinking without becoming product managers. He walks through the archer metaphor (better arrows, same need to pick the target), how homework works at the end of every episode, and highlights conversations to start with.
Also: Better with Kent, Kent's solo companion series on the same durable skills.
Homework
- Subscribe to Become an Epic Product Engineer in your favorite podcast app.
- Pick one episode to listen to first - if it wins you over, come back for the rest.
Resources
Guest: Kent C. Dodds