Mechanically Confident
summary
Claim: confidence comes from rehearsed routines and triggers not years of experience. Evidence: interns trip on familiar bugs until screen layout, editor color and keybinding habits stabilize their fixes. Examples: Steph Curry focuses on free‑throw mechanics and rhythm during a 48–49 streak; a pilot follows a checklist and lands with a blown engine. Built and tested: a small initiative tracker prototype using one‑time unique URLs to avoid auth complexity and observe divergent team decisions.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:03Confidence as habit
- 3:51Window placement habits
- 6:22Routines for confidence
- 7:24Curry’s free-throw habit
- 8:27Shults’ calm under pressure
- 10:16Honnold’s preparation
- 16:44Confidence through prep
- 17:48Routines for daily tasks
- 19:11Layering experiences
- 20:16Hall’s memory habits
- 23:48Routines to overcome fear
- 24:30Designing routines
- 25:13Triggers and rewards
- 26:18Commitment to follow through
- 27:21Empowering teams
- 27:42Celebrate failures
- 28:45Refine habits
- 29:26Perspective for learning
- 31:56Context for code
- 33:00Context in teams
- 34:03Commitment builds confidence
- 35:50Q&A
related talks
27mInterview with Confidence
26mTake a step back
28mI Have No Idea What I'm Doing
47mDeveloper under influence
30mCode, Confidence & Conquering Self-Doubt: Breaking Impostor Syndrome in Tech
01h 08mKeynote: Start Here: Mindset Shifts and Tools for Building Career Confidence
42mTester’s Mindset: Rethinking Software Testing Through Mentorship
38mBe the best You - One developers journey to fight the Imposter Syndrome