When I tell people I've been everything from an English teacher to a software architect to a theater actor, they usually respond with confusion. "How did you plan that trajectory?" The honest answer? I didn't. While I wouldn't necessarily recommend it as a strategy, that apparent lack of focus has had unexpected benefits.

David Epstein's "Range: Why Generalists Triumph in a Specialized World" helped me understand why. The book challenges early specialization, arguing that in complex environments, breadth of experience can complement depth of specialization.

The unexpected connections

Every seemingly unrelated experience has contributed to my engineering practice. Epstein calls this "analogical thinking" (applying solutions from one field to another).

Theater taught me about ensemble support and collective ownership, skills directly applicable to engineering teams. Banking compliance, once pure bureaucracy, became invaluable for building traceable systems. Academic research's experimentation mindset now helps me approach production problems systematically rather than just optimizing existing solutions. Teaching forces you to break down complex concepts and adapt to your audience, skills that turn out to be essential everywhere from code reviews to sprint planning.

For years, I felt somewhat guilty about this scattered approach. While colleagues spent evenings coding side projects, attending meetups, or contributing to open source, I was often found struggling to make chord shapes on a guitar, find the right lens settings on my camera, diving into psychology and management books, or making pizza for the 200th time because the mozzarella still didn't melt the right way. I worried I wasn't "engineer enough" compared to peers who lived and breathed code 24/7. The tech industry's culture of total immersion made my broader interests feel like distractions rather than assets.

This guilt intensified at work where I found myself gravitating toward variety rather than deep specialization. In my years of service, I touched almost every major service codebase, data processing, orchestration, infrastructure, CI/CD, testing, backends, frontends, and whatnot. I always looked forward to the next problem to solve and was comfortable switching teams or projects as needed. Eventually, I also got involved with management, marketing, sales, hiring, recruitment, business analysis, documentation, support, leadership, team building, and more. While others built deep expertise in specific domains, I seemed to be collecting experiences like breadcrumbs across the entire organization.

Each detour added nodes to the web of patterns I view the world through.

Why being a generalist actually works

What Epstein's research suggests (and my experience seems to support) is that generalists succeed not despite diverse backgrounds but because of them. We're not necessarily competing with specialists on their turf; we're often playing a different game.

The tech industry talks about "T-shaped" professionals, but I've found it's more like a comb: multiple spikes of expertise connected by broad understanding. The value isn't any individual spike. It's understanding how they connect.

Over time, this breadcrumb trail of experiences gave me something unexpected: a bigger picture of how things worked, and why they were a certain way. When debugging a CI/CD pipeline, my frontend experience helped me understand user impact. When designing data processing workflows, my infrastructure background informed capacity planning. When leading teams, my varied technical exposure helped me ask better questions and spot integration challenges before they became critical issues.

Modern challenges rarely fit one domain. Building AI-powered systems requires understanding ML, architecture, UX, business constraints, and team dynamics. Specialists excel at pieces, but someone needs to see how it fits together.

The value isn't knowing everything deeply. It's knowing enough about many things to recognize patterns, transfer solutions, and connect dots that might not obviously be related. Epstein talks about the importance of a "sampling period" (early career wandering that seems random often builds this invaluable perspective).

As AI increasingly handles specialized tasks, the advantage shifts to integration. LLMs can write better code than me, but they can't (yet) recognize that stakeholder resistance might mirror adoption challenges from completely different contexts, or that solutions from teaching might apply to system architecture. This is where generalists add value: in the spaces between specializations, in connections that aren't immediately obvious.

What this means for your journey

If, like me, maybe you feel like you've been wandering, maybe that's exactly what you needed. A few things I've learned:

  • Collect experiences deliberately. That unrelated side project might teach transferable patterns. I didn't expect teaching to influence stakeholder management, but it did. Similarly, working across different technical domains revealed patterns that weren't obvious from within any single specialty.

  • Document connections. Keep notes on patterns across domains. These connections become your unique value.

  • Resist early specialization pressure. Broader sampling often leads to better eventual performance.

  • Own your narrative. Don't apologize for zigzag paths. Different experiences contribute to how you tackle your current work.

  • Look for integration opportunities. The best solutions often come from unexpected sources.

Not lost, just taking the scenic route

My wandering wasn't aimless; it was preparation for problems I didn't know I'd face.

Epstein's "Range" gave me vocabulary for something I'd felt: in our complex field, integrating across domains has real value. We need specialists and generalists. In a world of increasing specialization, productive wandering can be its own specialization.

The path forward isn't choosing between breadth and depth. It's strategically collecting both and understanding how to integrate everything into something uniquely valuable.

After all, those who wander aren't necessarily lost. They might just be building a different kind of map.