The Industry Standard hoax: How Engineers Can Steer Product Decisions
summary
Claims that the industry standard hoax matters: engineers get concrete tactics to challenge "we must copy Amazon" thinking, compare multiple real examples, and weigh product fit against legacy tech and cost (tokens and billing models like Claude subscriptions are cited). The talk gives concrete tradeoffs, a process for disagree and commit, and real conference scale — 5000 Software Engineers 86 countries 1,023 Engineering Teams — so watch if actionable counterexamples and migration steps matter, skip if only high-level pep talk.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:05Why standards carry weight
- 2:49Copying big players
- 7:08Escaping comfort zones
- 8:53Big players aren’t best
- 10:59Industry-specific examples
- 11:40Evaluating product fit
- 13:45Customer value vs constraints
- 14:31Engineer’s product mindset
- 15:13Handling disagreement
- 16:40Final thoughts & Q&A
related talks
44mBehavioral Software Engineering
15mIt Works on My Machine: Why Engineers Are Misunderstood (and What They Can Do About It)
09mInterview with
25mBeyond Code: The Power of Thought Leadership in Engineering
18mFrom developer productivity to engineering impact
40mWhy Engineer Voices Don’t Get Heard — Practical Tips for Engineers to Influence Product Decisions
22mWhat the Best Engineering Leaders Do Differently
17mThe Soul of Engineering: How to be the Solution