AI summary by TwinMind
No Dev Will Admit This (The Secret To Getting Good At Code)
Theo - t3․gg
5m 12s
Introduction & Background
- Theo introduces himself as someone who likes skateboarding and coding
- One activity made much more money than the other
- Both required similar skills and mindsets
- Focus: how skateboarding made him a better developer
Skateboarding Culture & Failure Resilience
- Common theme among trick-focused skaters: comfortable throwing themselves at ground
- Best skaters not most gifted physically, but most comfortable with falling
- Key skills: getting back up after falls
- Resilience: hitting ground, ignoring pain, trying again
- Failure techniques: learning to fail safely
- Avoid injury when attempting tricks
- Gather necessary inputs/analysis to understand what went wrong
- Adjust and try again based on learnings
Professional Skateboarding Persistence Examples
- Most skaters take many tries to land tricks (not just 10 attempts)
- Professional skate videos: each trick can take days to film
- Typical scenario: skate spot for 4 hours, don't land trick, get kicked out by police, return days later for another 4 hours
- Well-documented instances of specific tricks taking years to land
- Skaters work on "impossible seeming tasks" while over-analyzing every failure detail
Case Study: Jaws and the Lyon 25
- Aaron "Jaws" Homoki attempted ollie down Lyon 25 (biggest stair set attempted)
- First attempt: tore ACL and MCL
- Didn't stop him - returned to France 2 years later
- Brought father for support in case of injury
- Technical detail: used deodorant stick to smooth board-wheel connection
- Prevents wheel bite from landing force
- Shows extreme attention to detail required
- Combination of support networks and technical preparation essential
Skateboarding Success Factors
- Building support networks and trust relationships
- Surviving hard moments feeling like "utter failure"
- Ability to step back and realize failure isn't personal
- Identifying small adjustments that can make tricks work
- Balance of emotional support and technical problem-solving
Programming Parallels
- Defining characteristic of great programmers: willingness to fail, be wrong, learn from it
- Never found great programmer who wasn't exceptional at being wrong and learning
- Must embrace failure that comes with trying new/hard things
- Most important characteristic when interviewing candidates
- Interview focus: how people handle things they don't know
- Do they experiment?
- Do they ask questions?
- Are they okay with not knowing?
- How do they figure out what didn't work?
Engineering Success Through Failure
- Success in engineering defined by long series of failures
- Personal examples:
- Dozens of failed interviews before first job
- Hundreds of companies that didn't accept applications
- Every cool project: dozens of attempts to make it work
- Hundreds of rewrites of individual lines
- Most code lines aren't perfect initially
- Learning from failures leads to adjustment, growth, success
Mindset Shift Recommendation
- Be proud and excited by failure as growth opportunity
- Days without failure = days without growth
- Hard to grow as engineer without "hitting pavement"
- Preventing failure is overrated
- Embracing failure is criminally underrated
- Failure justifies why software is buggy, but message benefits those who understand it
