Just Don't Lick The Cookie
summary
An hour and 45 minute session names concrete dysfunctions—cookie licking, plin, bike shedding, yak shaving—and shows fixes that actually work: de-assign stale bug tickets, require public commitments with dates, run lightweight quarterly reviews, use code tours, pair programming and code review to raise the bus factor. Workshop groups (four to six each) surface patterns and produce reporters’ notes. The claim is pragmatic: naming patterns and applying simple structural and social tools reduces recurring volunteer friction and unfinished work.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:35Session goals
- 8:44Diagnosing community problems
- 20:02Exit voice loyalty
- 29:39Common dysfunctions
- 47:01Group discussion
- 1:00:02New dysfunctions
- 1:14:00Wrap-up
related talks
42mLightning Talks
17mDiscussion - Protocols, Session 2
20mThe road to developers' hearts
42mSponsored Session: Dependencies: Do's and Don'ts
27mSecurity: The Thing That Everyone...
49mEverything is Terrible: Three Perspectives on Building, Configuring, and Securing Software
30mSecurity by Stealth
31mDo You Even Tech Anymore: Management & Leadership in Security?
