How to Product Being a Productive Product Engineer
summary
Conference cites 20% of developers happy and claims productivity hinges on three measurable levers: shorten feedback loops with CI/CD and automation, protect Flow by batching meetings and carving no‑meeting days and AMAs, and cut extraneous cognitive load by preferring proven stacks and reviewing code periodically. Concrete pain: Flutter vs React Native hot reload differences and a real case of Firebase native dependency conflicts causing runtime errors; an RFC once waits one‑month for review. Recommendations: stick to boring architecture, scale only when needed, and enforce clear tickets, tests, and documentation.
AI-written summary · about
chapters (24)
- 0:00Introduction and speaker intro
- 2:11Today's agenda overview
- 2:53Developer unhappiness and its causes
- 4:36What is developer experience
- 5:48Understanding feedback loops
- 7:33Shortening feedback loops
- 11:03What is Flow State
- 12:46Improving Flow State
- 17:44What is cognitive load
- 18:46Types of cognitive load
- 20:54Reducing cognitive load from tools
- 23:02Reducing cognitive load from information
- 24:06Reducing cognitive load from processes
- 25:28Architecture and cognitive load
- 27:41Limiting responsibilities
- 28:45Evolving tech stack strategically
- 31:11Retrospective code reviews
- 32:37Writing clean code
- 34:24Defining team norms
- 35:32Tools to reduce cognitive load
- 36:55Daily productivity techniques
- 37:39Recap and key takeaways
- 39:48Where to learn more
- 40:30Q&A
related talks
32mBUILDING MOBILE PRODUCTS THE HAPPY WAY!
33mMeasuring Developer Productivity: the good, the bad and the data
48mEnding Keynote: 7 Principles of Productive Software Developers
37mPersonal Developer Productivity Tips It's the small things
01h 02m10x_productivity_for_developers_and_architects
21mHow to Increase Developer Productivity and Happiness
50mThe Effective Developer - Work Smarter, Not Harder
45mSeven Principles That Will Boost Your Developer Productivity