Expediency & Fluency
summary
Argues that productivity depends on balancing quick, minimal solutions with robust repetition and automation, recommending a design sprint that produced a live profile page delivered behind a toggle which users opened and fed back immediately. Calls for trunk-first development, one-hour deploy capability, dark/canary releases, contract tests and extensive CI to avoid blocking dependencies. Recommends teams under ~7 people, collective code review instead of PR battlegrounds, and never compromising engineering quality while trimming functional scope.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:12Customer demands vs quality
- 7:27Release often and feedback
- 11:04Kanban for remote work
- 13:33Dependencies and delivery
- 15:59Team size and processes
- 17:26Feedback and rollouts
- 19:11Retrospectives and improvement
- 19:31AI in software development
- 20:54Q&A: Trunk-based development
- 21:37Q&A: Hiring communication
- 22:41Q&A: Code review
related talks
21mNeed for speed - Moving fast as a software engineer
28mHow to prioritize dev experience in the development process
29mLazy Engineering
34mBuilding a Culture For Developer Productivity
58mTechnical Practices that Take Time but Save Time
38mBuilding a high quality product
31mThe Effective Developer - Work Smarter, Not Harder
54mDeveloper experience platforms