Wading In The Shallows

The Shallows vs. The Deep End

Tim introduces the concept of "wading in the shallows" as a metaphor for people who think they've gone deep on a topic after only casual involvement — armchair quarterbacks, WebMD doctors, people with surface-level knowledge and outsized confidence.

He contrasts this with topics he's genuinely gone deep on:

• Computer science — from high school through a hardcore engineering degree, including wiring breadboards for logic gates
• Game development — over four decades of hands-on work, nearly into his fifth decade
• Business — actually running a company with employees, payroll, and HR (not just theorizing about it)
• Chocolate — his blog has over 2,000 entries

The Lesson of Going Deep

The biggest lesson from truly mastering a subject: what you think you know at the start is not what you'll discover later. There's a deceptive transition where you quickly feel like you understand everything, but putting knowledge into practice reveals enormous gaps.

Teaching a subject is the fastest way to discover what you don't know. Tim suggests he may do a full video on his teaching experiences, but the core point is clear: if you want to find your blind spots, try explaining the topic to others.

As you push deeper, you eventually learn those missing pieces — and you look back at your earlier confidence with a kind of amazement. Tim calls it "unearned confidence."

Fallout: Lightning in a Bottle

Tim uses Fallout as a concrete example. For many team members, it was their first time in a lead role, their first RPG built from scratch, and their first original IP. They were confident — but shouldn't have been. They got lucky: the right people at the right time, lightning in a bottle. They were in the shallows, and "at any moment a shark could have come along."

Knowing What You Don't Know

There's a middle ground between the shallows and true depth: wading in far enough to realize how much you don't know. Tim describes this experience with several fields:

• Writing — he's tried it, knows he's not good at it, and respects those who are
• Network programming — quickly discovered vast unknowns
• Graphics programming — had some success (the original Fallout engine was his), but between color blindness and the sheer breadth of the field, he recognized when to hand off to experts (as he did at Carbine Studios)

This middle-ground awareness is valuable: it lets you recognize and appreciate people who are truly skilled in those areas, and it qualifies you to advise and manage them even if you can't do the work yourself.

Leadership Doesn't Require Being the Best

A key leadership insight: being a lead doesn't mean being the best person in the room at every skill. It means understanding what's involved well enough to manage people who are better than you. You need to see the forest even if you don't understand every tree.

The Swim Instructor, Not the Lifeguard

Tim frames the experienced person's role as a swim instructor rather than a lifeguard. When someone new is wading in and starting to feel confident, you don't need to be rude or dismissive — but you should keep their comments in perspective. Your job is to:

• Guide them into deeper water
• Point out the rip tides and sharks
• Help them learn to swim in the deep end without drowning or running back to the beach

The Alternate Title: "The Beach Is Not the Ocean"

Tim's alternate title captures the whole message. Standing on the beach looking at the water — or even wading up to your ankles — will never let you understand the ocean. You have to go deep. And you can't go deep on everything, so choose wisely: understand what you've truly mastered versus what you've only sampled, and maintain that self-awareness in your work.

References

• Tim Cain. YouTube video. https://www.youtube.com/watch?v=HgiVDrTd8Mo