What I've learned on Being a better Engineer from being a Product Manager
summary
Claim: ask four concrete questions before coding — who is it for, what does success look like, what is the minimum value I can deliver, what else — and use metrics to decide. Examples: a cybersecurity product wastes 16 months and market fit, a marketplace alters its buyer–seller inbox, adds an emoji component with lazy load and sees a 400ms slowdown that must be judged against whether meaningful conversations increase. Tools: MVP iterations, business metrics, and tradeoffs like a 15% dev-time refactor.
AI-written summary · about
chapters (4)
related talks
15mPut On Your Product Hat When Championing an Internal Tool
44mPlatform Engineering is All About Product
44mProduct 101 for Techies and Tech Teams with Amanda Savluchinske
32mDeveloper productivity 2.0
23mUsing Data to Bridge Product and Engineering Teams
38mProduct and Experience Metrics: What Every Programmer Should Know
38mTools and methods are killing your products
18mFrom developer productivity to engineering impact