Early years

  • Grew up programming; his dad was a software engineer, which lowered the barrier to entry. Started working out of high school, founded a company that got acqui-hired, then bounced around as a consultant and founded more companies before ~6 years of full-time open source 7:04.
  • Minecraft modding was the formative experience: he worked on a modding framework itself, built mods, and ran a ~100-player server where he used mods to create "interesting situations" to observe how people behaved — sandbox design over gameplay 7:52.
  • The modding community lived on IRC and included very senior programmers who weren't career-motivated — talented people funneling their energy into Minecraft — and he learned a lot from them in a couple of months 8:31.

Early startup lessons (Ride Health, ~2017)

  • Head of engineering at a transportation/healthcare startup that grew to ~20 people and "ended up in a disaster" — though he met his wife there (she was head of product): "better than a startup exit" 9:22.
  • Key takeaway: the "bunch of young people building a startup" stereotype is the exception, not the rule. Everyone was in their 20s, insecure, and it played out as politics and drama. He wouldn't invest in all-young teams 9:44.
  • Startups are intimate and intense; if you're not fully developed as a person, insecurities show up at work as conflict. He feels his own brain didn't "settle" until ~26, and the change felt like night and day 10:56.

Why not big tech

  • In the early/mid-2010s big tech was the prestigious path, but he "couldn't get it together" to grind the structured interview process — good programmer, but not willing to study for the competition level required 11:56, 12:38.