Context is Key: The Value of Knowing Why
summary
Claim is blunt: coding without context is masturbation — write code knowing why it exists, how it fits, and what user experience matters. Cites operational tools and signals: metrics, deployment topology, on-call behavior, SRE practices; a concrete check is putting Tinder on our phones to see real UX, not just dashboards. Notes surprising stat: only ~20–30% truly needed cloud migration. Emphasizes asking why, mapping buyers, and documenting decisions so changes actually work.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 2:11Who I am and my background
- 4:59Why context matters
- 7:27Context in development
- 10:40Requirements aren't enough
- 13:07Context in product management
- 17:19Context in pre-sales
- 18:23Leadership and context
- 22:12Context in careers
- 27:09Burnout in tech
- 29:19Vulnerability at work
- 31:46Asking why is key
- 33:19Q&A: Junior dev context
- 34:24Q&A: Breaking silos
- 37:07Q&A: Building relationships
- 39:10Q&A: Junior devs vs architects
- 41:48Q&A: BJJ context
- 44:10Q&A: BJJ history
- 47:05Q&A: Criticism rapport
- 49:35Q&A: Junior stigma
- 51:45Closing
related talks
18mShould coders design?
05mWhy Why Why
05mContext-Driven Practices
33mWhat it takes to become a great developer!
01h 32mKeynote: It Depends..
40mBeyond Code: Skills For Impactful Development That Makes a Difference
28mBut Why? The Storybook Of Learning The Importance Of Asking Questions.
17mArchitects of Experience: Creating Connections Beyond Code