Build the Right Thing: Product Engineering (Part 1) — Kent C. Dodds, EpicProduct.engineer
In the era of advanced AI agents, the value of software engineering is shifting from implementation (coding) to product judgment. The core thesis is that as development becomes commoditized, the most valuable skill is 'Product Engineering'—the ability to define and validate the 'right thing' to build. Product engineers must connect customer needs to technical constraints, focusing on defining the data model, workflow, and the smallest useful slice of a system, rather than simply executing a ticket to spec.
Key takeaways
-
The Shift in Engineering Value
25:43
As AI agents level the implementation playing field, the differentiator is no longer coding ability but the judgment required to determine if a problem deserves a software solution. The focus moves from 'Can we build it?' to 'Is it worth building?'
-
Defining Product Engineering
20:46
Product engineers must take ownership of the upstream process, looking beyond the immediate request to understand the user's core problem. This involves making technical decisions regarding the data model, workflow shape, observability, constraints, failure modes, and identifying the smallest useful slice of the system.
-
Validating Ideas with The Mom Test
35:09
To validate an idea, avoid asking users to evaluate the solution or diagnose the problem. Instead, ask behavioral questions like: 'When was the last time this happened?' and 'What did you do instead?' and 'What did it cost you to do that?' This reveals actual pain points and the cost of existing workarounds.