Taste Driven Development
summary
Quality is framed as an emotion that comes from tiny details, not metrics; the team treats quality as urgent: bug triage averages 44 minutes triage and most issues are fixed within two days, aiming for near-zero bugs. A weekly half-hour ritual called quality Wednesdays surfaces small fixes, producing ~1,000 polish improvements and syncing team taste. Heavy processes and OKR-driven A/B focus are called out as liabilities; instead investment in empathy, ownership, and design choices that shape user behavior proves the concrete path to products that feel right.
AI-written summary · about
chapters (9)
- 0:00Taste Driven Development intro
- 2:41Quality as emotional experience
- 3:51Why quality matters
- 4:54Quality traits hierarchy
- 6:41Taste and quality role
- 9:56Dangers of metrics reliance
- 14:43Linear's quality practices
- 18:18Behavior beyond features
- 19:22Taste Driven Development summary
related talks
20mCrafting quality that endures
29mTaste & Craft: A Conversation with Tuomas Artman, CTO Linear & Gergely Orosz, @pragmaticengineer
21mChasing Quality
26mCognitive approach to software quality
09m"The Tester’s Role: Balancing Technical Acumen and User Advocacy"
37mDavy Kenis: QA No More: Revolutionizing Software testing
33mHow Minimalism Helps Build High-Quality Products
24mPanel Talk: Integrating UX for Improved Product Development