Learning as an Infinite Game
Why Rushing Will Burn You Out
Someone messaged me last week asking about breaking into data science. But instead of asking about Python or SQL, their question was: "What's the most efficient 6-month program that can take me from zero to hired?"
When I suggested starting with a basic SQL course, they said: "That's 6 hours of content. What if it's the wrong approach and I waste my time?"
They were paralyzed by the thought of spending 6 hours on something that might not be perfect. They wanted guarantees before starting anything.
This happens constantly.
I get questions like this regularly from people wanting to break into data roles. They're not stuck on the technical concepts—they're stuck researching the "optimal" learning path. They spend weeks comparing bootcamps and building perfect roadmaps. Many haven't written a single line of code.
The irony? While they're optimizing, others are already learning.
The Finite Game Trap
Most beginners approach learning like a finite game—something with clear rules, a defined endpoint, and winners and losers. In this mindset:
There's a "correct" sequence of skills to master
Completion means you're "ready"
The goal is to reach the finish line as quickly as possible
Efficiency is everything because time is running out
This leads to some predictable behaviors:
Analysis paralysis. Spending months researching the perfect bootcamp instead of starting anywhere.
Course hopping. Jumping from program to program, looking for the one that will "finally make it click."
Burnout sprints. Trying to absorb everything at once, then quitting when it becomes overwhelming.
Impostor syndrome. Feeling behind because others seem to be moving faster or know more.
I've watched brilliant people give up not because the material was too hard, but because they were sprinting in what's actually a marathon.
Learning as an Infinite Game
But here's what every successful person in data eventually realizes: this isn't a finite game. It's an infinite game.
In infinite games, the goal isn't to win—it's to keep playing. The rules can change. There's no finish line. Your job isn't to reach the end; it's to stay in the game as long as possible.
When you view learning this way, everything changes:
There's no "perfect" starting point. You just need a starting point.
Completion isn't the goal. Continuous improvement is.
Efficiency matters less than sustainability. Can you keep this up for years?
Everyone is always learning. Even senior engineers are figuring out new technologies.
The data scientists and engineers I know who are thriving in their careers? They're still learning. The tools change. The problems evolve. New frameworks emerge. They never stopped being beginners in some areas.
What I've Learned from Coaching Career Changers
After working with dozens of aspiring data professionals, I've noticed clear patterns between those who succeed and those who burn out:
The ones who burn out:
Rush through foundational concepts to get to "advanced" topics
Skip projects because they want to cover more ground
Constantly compare their progress to others
Treat each course or tutorial as make-or-break
Quit when they hit their first major obstacle
The ones who succeed:
Start somewhere, even if it's not perfect
Build small projects to reinforce what they're learning
Focus on understanding, not just completion
Expect to revisit concepts multiple times
View obstacles as part of the process, not signs they're not cut out for it
The difference isn't intelligence or background. It's mindset.
Efficiency vs. Effectiveness vs. Sustainability
We often talk about efficiency versus effectiveness in learning, but there's a third dimension that matters even more: sustainability.
Efficiency is about speed—covering material quickly.
Effectiveness is about depth—truly understanding what matters.
Sustainability is about longevity—maintaining your learning over time.
In a finite game, efficiency wins. Get to the end as fast as possible.
In an infinite game, sustainability trumps everything. Because if you burn out and quit, efficiency and effectiveness become irrelevant.
This is why I tell people to pace themselves. Yes, there's value in being efficient when you're trying to change careers. But not at the expense of sustainability.
Better to take 12 months to build solid fundamentals than to burn out after 3 months of cramming.
Practical Shifts for Infinite Game Learning
If you're feeling overwhelmed by your learning journey, here are some mindset shifts that might help:
Start with "good enough" instead of "perfect." The best course is the one you'll actually complete, not the one with perfect reviews.
Celebrate small wins. Finished that 6-hour SQL course? That's progress. Built a simple dashboard? That's a portfolio piece.
Expect to relearn things. You won't master concepts the first time through. That's normal, not a sign of failure.
Focus on doing, not consuming. Build projects, even simple ones. Apply what you're learning immediately.
Compare yourself to past you, not others. Are you better than you were three months ago? That's what matters.
Plan for plateaus. Learning isn't linear. You'll have periods where nothing seems to click. Push through—breakthroughs are usually just around the corner.
The Long View
I've been working in data for over a decade, and I'm still learning. New tools emerge constantly. Business problems evolve. The field keeps changing.
The people who thrive aren't those who learned everything perfectly from the start. They're the ones who developed sustainable learning habits and never stopped adapting.
Your goal shouldn't be to find the most efficient path from zero to hero. It should be to develop the mindset and habits that will serve you for decades.
Because in data—like most knowledge work—the learning never really ends. And that's not a bug, it's a feature.
The real question isn't: "What's the fastest way to learn everything I need?"
The real question is: "How can I build a sustainable approach to learning that will work for the next 20 years?"
Answer that, and you're ahead of most people still looking for shortcuts.
Start Somewhere
If you're just getting into data, here's my advice: pick something and start. Take a basic course, work through it completely, and build something small with what you learn.
Don't worry about whether it's the "best" course. Don't stress about covering everything. Don't compare your day one to someone else's day 1000.
Just focus on not quitting. Everything else follows from that.
What's your experience with learning burnout? Have you found yourself caught in the efficiency trap? I'd love to hear your story—reply and let me know what's worked (or hasn't worked) for you.