AI summary by TwinMind

Please Stop Asking For Mentorship

Theo - t3․gg

9m 56s

Personal Experience with Mentorship

  • Never had traditional mentor as software dev
  • Had helpful managers at moments but no consistent go-to person
  • Believes lack of mentor contributed to success
  • Software dev success = handling failure well, not who you know

The Mentorship Request Problem

  • Receives couple DMs weekly asking "will you be my mentor"
  • Two valid interpretations:
    • Already mentoring through content (valid)
    • Requesting dedicated personal time (unrealistic)
  • Can't dedicate individual time to random audience members

Cost and Economics of Mentorship

  • Video content = efficient: one creation helps thousands/hundreds of thousands
  • Individual mentorship = expensive: more time, often less results
  • Requires understanding individual needs, communication styles
  • Takes ton of time to figure out what individual needs
  • Current content creation motivated by desire to help, not money
  • Could make more money in engineering career or business

Learning Through Peer Exposure vs Mentorship

  • Best learning at Twitch through lunch conversations
  • Surrounded by smarter, more experienced engineers
  • Heard thoughts on new tech, outages, current projects
  • Value came from exposure to different perspectives
  • Seeing experienced people debate/push back on ideas
  • Helped build own stances rather than copying one person
  • Traditional mentorship would have limited this growth

Problems with Traditional Mentor-Mentee Relationships

  • Both sides get screwed
  • Mentee just follows mentor's advice without questioning
  • Even with disagreement, not mentee's place to push back
  • Reduces likelihood of finding what's right for them
  • Example: 1 hour solving problem vs 2 hours call + 3 days code review

Quality Issues with Free Mentorship

  • High-quality mentors won't work for free due to expense
  • Available free mentors often lower quality
  • Still valuable to participate in communities
  • Can ask specific project questions and get responses

The Failure Problem

  • Software dev involves constant failure
  • Need to get good at pushing through failures independently
  • Shouldn't lean on others when failures happen
  • Support groups valuable (why university/bootcamps work)
  • Mentorship shouldn't be solution for loneliness or feeling lost

Goal Setting and Self-Direction

  • Bad goals: "want to be programmer" or "learn JavaScript"
  • Need specific goals around things you understand
  • Theo's example: hosting Minecraft server for friends
  • Required learning git, Java, server hosting, SSH, tmux, screen
  • Knew what success looked like even without understanding parts
  • Could join communities and ask informed questions

Show Your Work Philosophy

  • Don't spam random commits
  • Build demos with interesting technologies
  • Post online with context about what you built
  • Example: "built demo with TanStack Router for X purpose"
  • When asking for help, show effort and provide specific code links
  • "Can you be my mentor" = someone fallen behind asking to be caught up

Success Story: Ethan Niser Example

  • Early community member who shared cool projects
  • Built next-type-safe-URL bringing type safety to router
  • Created Beth stack and YouTube channel
  • Didn't ask permission or how-to questions
  • Asked if Theo would make video, when told no, did it himself
  • Success came from learning lessons and applying them creatively
  • Responded because of exciting work, not mentor-seeking

Key Principles for Success

  • Excitement and energy must come from within
  • People seeking mentors often lack internal drive
  • Another person will never be reason for developer success
  • Others can be tools in toolbox but you define the path
  • Need to realize path is wrong and change course multiple times
  • Must find interesting things that drive you through hard parts
  • Learn to lean into failure rather than avoid it
  • Share lessons learned from failures

Final Message

  • Stop seeking mentorship, start seeking interesting projects
  • Need to push through failure instinct independently
  • Once you do that, you'll naturally work on interesting things
  • Don't need permission to learn - just go build and learn
  • Come back when you have cool things to share

TwinMind

Get summaries like this for your own meetings

TwinMind takes notes in the background during meetings, lectures, and calls, then writes the summary for you.

Free plan to get started

No bot joins your calls

Phone, desktop & Chrome apps

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome