"Success is stumbling from failure to failure with no loss of enthusiasm."
— Winston Churchill
The path to becoming a professional is like climbing a mountain. But the barrier in learning usually isn't the height of the mountain. It's the steepness of the walls.
Yosemite's Half Dome and El Capitan sit facing each other across the valley. Half Dome sits at a higher altitude, and yet tens of thousands summit Half Dome each year while El Capitan remains one of the hardest climbs on Earth. The difference? Half Dome has a route around the back, with switchbacks, a trail, and cables up the final ascent. El Capitan is a sheer face. Alex Honnold's ropeless ascent film, Free Solo, was a blockbuster because of how impossible it was.
Our work as educators is to build the route, not lower the mountain.
How many potential careers have been cut short because someone believed too early that they didn't have what it takes? How many kids decided they're "not math people" after one bad test or a careless comment? How many nascent coders walked away after a single error message and assumed they weren't the kind of person who could do this?
A teacher once pulled me aside during a visit to a KIPP school in the Bronx. "See that kid over there?" She pointed to a lanky teenager hunched over a laptop, completely absorbed. "He struggles from 8 AM to 4 PM every single day of his life in school. Every. Single. Day. This is the first time we've seen him come alive and feel successful."
I had spoken to him for a while. He was building a platformer game, testing jumps, laughing. He was telling me about his game at 80 miles an hour. About all the things he was building. He wasn't struggling. He was playing. He was building. And in doing that, he was learning.
That moment captures everything about what we're building at Endless Studios. We've systematically broken the journey from complete novice to professional game maker into five distinct phases. Each phase has its own goals, challenges, and solutions. And they overlap seamlessly, so you can enter wherever you are and progress at your own pace.
We call this the S-Curve to Professional. Think of it as five ridges that flow into each other, making up one ridgeline from base to summit.
In the stacks of notebooks I’ve filled over the years, there’s one diagram that shows up again and again. I draw it in almost every meeting I have. It’s a simple skill curve, running from novice in the bottom left to professional in the top right. Along that curve, I sketch five circles. They are these five phases along a single, continuous journey toward mastery. I repeatedly come back to this drawing because it’s useful. Everything that we do lives somewhere along this curve. Here’s the S-Curve:
The S-Curve to Professional. Five overlapping phases that guide learners from novice to professional.
In our world, the five phases look like this:
The Trailhead: At the beginning of a journey, wonder sparks yearning. The Switchbacks: To help them climb, we scaffold, handhold, and guide. i.e. We teach. The Long Ridge: Along a multi-year long ridge, learners do the work of building together. In community. The Alpine Push: When ready, learners become leaders, owning their outcomes. The Summit Ascent: On the summit ascent, learners apprentice with professionals.
Here’s what it looks like in detail, circle by circle, stage by stage, ridge by ridge:
The Goal: Get people excited. That's it.
Every climb begins not with discipline, but with wonder. Something dazzling must draw the climber to take the first step: a beautiful view, a flower at the trailhead, the thrill of the unknown. In learning, that spark is passion. Passion is visceral. Passion is personal. And passion, for most young people, starts with play.
This is why we begin with games you can play. Not educational exercises dressed up as games. Real, delightful, full-fledged games. Before we ask a learner to build, we want to let them play. To place them in a world where they laugh, compete, get lost in fun. Only then do we reveal the hidden doorway: you can help make this.
That's the moment of ignition. When students realize they can alter the very games they're playing: design a level, add a character, change the rules, the shift from consumer to creator isn't theoretical. It's visceral. Suddenly, they're not just players in someone else's world.
This is why we built Endstar, our game creation tool. It's a tool that feels like a toy, as simple as Minecraft, as social as Roblox, as inviting as Mario Maker. Play becomes creation through dragging, dropping, and connecting. Every interaction unlocks more powerful tools, each one revealing how real game engines work.
We also need tools that run on the lowest-spec machines in the world, so we adapted Godot, an open-source game engine, into an incredible learning tool. The goal is to make the entry point as wide as possible, welcoming every child regardless of what device they have. We have built an open source collaborative game called Threadbare that welcomes students in as players, and then welcomes them in to contribute levels, art assets and even core gameplay features.
With these tools, we invite students into game jams. We make it easy for them to play with their friends at home and slip into creation without even realizing it. We also make it easy for teachers to do this in their classrooms so that we don’t need to be in the room. At this stage, the bar is simple: delight.
Students must feel like they can do it, and like the work is worth doing. Early wins matter. Our intro experiences unlock dramatic, rewarding moments, fireworks, portals, NPCs that talk back, doors that open with triggers. You don't start with syntax errors. You start with joy.
That boy in the Bronx? He wasn't an outlier. I've also seen an Emirati girl who signed up to draw characters, then realized she'd need to code to animate her art, and discovered she loved coding more than drawing. I’ve seen rooms full of students who drove across Jordan for this. And in students in game jams that got thirty minutes of sleep on the final night to win first place. Neurodivergent kids whose parents tell us that this is the most engaged they’ve ever seen them. These transformations happen when kids feel that first spark: I can do this. And it's worth doing.
These are the flowers at the trailhead. Each small win whispers: you belong here. This is Phase 1: Spark the passion and make the first wins feel possible.
The Goal: Teach real tools with the right support.
The first steps up any mountain are the most precarious. Early in the climb, the path is unfamiliar. People need help. A rope line here, a handhold there. In learning, this comes in the form of bootcamps, just-in-time teaching materials, and simplified tools, each of which can mean the difference between someone turning back and finding their rhythm.
Launchpads are roughly 6 - 12 week experiences where students learn the basics in the context of building something real. These aren't lectures. They're workshops. Students break into small teams of 4-5 people, with a designer, engineer, artist, producer, and they build original games.
The process is real: scope, prototype, test, iterate, polish, ship. Each student contributes a piece, a level, a feature, a character, and together they create something complete. Something they can show their friends. The product is a game, but the real prize is the feeling: I can actually do this.
These can be strung together. One Launchpad gets you over the fear of opening the tools. The next deepens a discipline like art or code. The next teaches you to work on open source teams. Each time, we scaffold a little less, until the leap into Phase 3 stops feeling like a leap at all.
Once passion is sparked, students need to make the leap into real tools: Unity, Blender, GitHub. That leap is hard. These are the tools used to build professional games and professional software, tools that require real sweat to master. But these tools are also where magic becomes possible. So we do what builders do: we build the route. We create scaffolding tools that make professional software approachable without hiding its power.
Endstar sits on top of Unity, making the engine inviting while revealing how it actually works. We've adapted Godot with block coding, game templates, and collaborative editing, effectively turning an open-source game engine into a training ground. We've built Threadbare, a massively collaborative game that teaches students how real open-source communities work: version control, branching, shipping code into shared projects. What This Enables: These tools make contributing feel reachable long before it feels natural. Students learn to collaborate, manage versions, and ship into shared projects. These are the rhythms of professional development. All of it serves one goal: make it comfortable to step onto the challenging terrain of real software development.
Teams get stuck constantly. That's when mentors step in. Sometimes it’s with a quick pointer, sometimes by pairing on tricky tasks, occasionally by supplying specialized assets. But the students do the work. They learn by doing, with just enough support to keep moving forward.
By the end of a first bootcamp, teams ship games: platformers, narrative adventures, 2.5D scrollers, simple shooters. Within months, students who knew nothing about coding or game engines are building complete games as part of a team.
That builds towards the ultimate goal: for them to contribute to projects larger than their own. The real world consists of people working on big projects. Students need to learn how to do that. So we guide them to add their work to a shared game world: designing a level, adding art, coding a feature, polishing an effect. For the first time, they step into the rhythm of open-source culture, contributing to something far bigger than they could build alone. This is the bridge between small-team projects and professional work. This all runs in a community on common infrastructure: a mentor pool, a skill tree, just-in-time learning resources, daily office hours, "gym-style" Zoom rooms where you can drop in and work. The Studio runs like a startup. It's always open, always active. Students can drop in whenever they're ready to work. A student stuck on a bug can drop into office hours, watch a relevant livestream, or grab a template from the library. Another working late can jump into a Zoom room and find others building alongside them. The gym is always open, and someone is always there.
This is Phase 2: Give structure and support so learners can make the leap into real teams.
The Goal: Build real games together. For years.
Phase Three is fundamentally different from Phase Two. Launchpads are time-bound programs. They begin and they end. Phase Three isn't really a phase. It's a community. It's ongoing. If you like what you're doing, you can just keep doing it for years. Building side by side with others. Growing from beginner to expert without ever leaving.
Mastery takes years. This is the space where you can earn that mastery. It is the heart of Endless Studios. This is where people become craftsmen and women, not through isolated projects, but through sustained practice on projects. If the apprenticeships of the ancient world took place in the blacksmith shops of the era, GitHub is clearly the modern workshop where software engineers forge their wares. I often say that GitHub is the world's largest school. This community, The Studio, is like the gathering place right in front of the workshop. It is the place where you can find projects to work on, people to work with, and find easy onramps into the heat of what's being forged within.
Here, beginners work next to experts, picking up habits and skills by proximity as much as instruction. Students form teams, join ongoing projects, contribute features or levels, and see their work woven into something larger. When one student ships a puzzle mechanic, another builds a dungeon around it. When an artist sketches a character, an animator brings it to life. The community itself becomes the classroom.
This is also where identity shifts. A player becomes a builder. A student becomes a contributor. A contributor begins to see themselves as a developer. Not because someone gave them a certificate, but because they shipped real code, art, and design into games others can play.
Participants usually start with smaller games built with friends or classmates. As skills grow, participants join bigger, persistent projects that are run like open-source software. We learned how good of a learning environment open source projects are when we built Endless OS. It's also how software is built, given that open source is inside of the vast majority of software. It's time students understand how it works. And as skills grow, students begin contributing to professional projects alongside real studios. These games have creative directors who hold the vision, producers who break work into tasks, and discipline leads (art, engineering, design) who manage contributions. Tasks are tagged by difficulty level so people at every skill level can contribute. Some tasks are assigned to trusted contributors. Others are opened as competitions with bounties attached.
There are two main types of contributions: features and levels. Features: Take Dragon's Apprentice, a dungeon-crawling adventure game where you craft magic spells using computational thinking. We had budget for core infrastructure and a handful of dungeons. But there are dozens of features we wished we had time for: smarter enemy AI, richer narrative, dynamic environmental art, swimming mechanics, weather systems. With a hundred contributors, we could add them all. One person might animate wind in the grass. Another might add swimming, which spawns new work: swimming animations, oxygen systems, wet clothing. Each feature creates more flexibility for future level designers.
Levels: When we built Dragon's Apprentice, we ran out of budget before we ran out of ideas. The game has potential for dozens more dungeons, but we had to stop. Opening it to the community lets anyone contribute levels using real tools. The community fills the map with dungeons, the best puzzles bubble up, and the most engaging ones take prominent places.
Some work on small teams, applying to join ongoing professional productions. Others compete in larger community challenges, with thousands vying to win an art asset competition or claim a featured level slot. Whether it's a small collaborative team or a massive open competition, the learning is the same: professional feedback on real work. This is where mentorship shifts. In Launchpads, mentors teach. Here, mentors collaborate. Studios give feedback not because you're a student, but because they need your contribution to meet their standards. You're not practicing for the real world. You're already in it. The more you contribute, the more you learn. The better your work, the more opportunities open up.
The hardest part? Self-direction. There's no curriculum to follow. You choose the project, claim the task, decide if you're ready. That ambiguity is uncomfortable, but it's the point. Agency is a skill. You learn it here.
Throughout this journey, participants progress through a skill tree, a map of capabilities across five core disciplines: Art (2D, 3D, animation, UI/UX), Design (game design, narrative, level design), Engineering (programming, systems, technical art), and Management (production, communication, leadership) and Entrepreneurship (strategy, marketing, data analytics).
Everyone needs base-level competency across branches. You don't need to be an expert programmer to be a great artist, but you need to understand how code works. The skill tree makes visible where you are, where you're going, and what's next. It helps students discover interests (you might enter thinking you want to code, then discover you love level design), and it helps mentors recommend appropriate tasks. Most importantly, it reflects how skills actually develop—both in how we learn and how the professional world works. You build broad competency while specializing in the areas where you thrive.
Like a long ridgeline, this community is where stamina is built, where friendships are forged, and where the climber stops worrying about cliffs, because they know they belong on the mountain.
This is Phase 3: Make real things together. Build for years. Forge your skills.
The Goal: You learn to lead.
As you level up, you become ready to be a leader. Someone who carries the map, chooses the line, and holds the rope for others. Every learner must experience being the leader, even of a small group, to truly gain the confidence that they can navigate the heights.
When I was in my teens, every member of my family went on Outward Bound, a month-long wilderness adventure. I loved it so much that I did two more of them in a program called NOLS. The National Outdoor Leadership School. For weeks, instructors taught us wilderness survival, team dynamics, technical skills. First through lectures, then through real challenges. The wilderness is full of plenty of them. Then came the crucial moment: Students voted on leaders for each squad, and those squads headed into the wilderness alone. I remember looking at my team, feeling the weight of responsibility for these lives entrusted to me. That leadership experience is precisely what we want to give people on their journey to becoming leaders in the professional world.
Practice feels fundamentally different when you're captaining the ship. Everyone needs experience at the helm, even of a small vessel, to serve well on larger crews later. One of the most valuable traits an employee can have is what Keith Rabois calls "barrels rather than ammunition." In battle, you need people who can point the ammunition rather than be the ammunition. Give them a target and they’ll hit it. That autonomy only comes through experience.
Most people don't lead major projects until late in their careers. The average first time manager is more than 35 years old. People spend decades following others' directions, then suddenly they're expected to lead. How can we expect people to become good leaders this way?
We must give youth safe opportunities to lead when they're young, with all the daily challenges unique to running their own projects.
Capstone projects are that opportunity. They are the culmination of everything that came before. Long-duration team projects with dedicated teams, special mentor guidance, and one goal: launch a full, playable, feature-complete game.
These are not classroom exercises. These are real games built to ship.
These are ambitious. Not just a few levels or a small mechanic. Full games with beginning, middle, end. Multiple systems working together. Polish. Art direction. Narrative arc.
Mentors are available but distant. The team must figure it out. When they get stuck, they have to decide: Can we solve this ourselves? Do we need help? What kind of help? Learning to ask for the right help at the right time is itself a skill.
Leadership is hard. Making decisions when there's no clear answer is hard. Saying "no" to a teammate's idea is hard. Holding people accountable is hard. Managing scope, deciding what to cut when you're behind schedule, is excruciating. We see teams implode. We see leaders who can't let go of control. We see leaders who abdicate entirely. We see teams ship games that are technically complete but no fun to play because they lose sight of the goal. That's okay. That's the point. Better to fail leading a capstone project than fail leading a team at your first job. The stakes here are lower. The lessons are the same. It is in this that real leadership is learned. Most people don't get this until their late twenties. Our students get it at seventeen.
Our goal is for the best capstone projects to get invited to work with the Pro Studio (Phase 5) to polish for commercial release. But even if they don't, every student leaves with a portfolio piece, with leadership experience, and with the confidence that they can take an idea from concept to shipped product.
This is Phase 4: Become the leader. Carry the weight. Deliver anyway.
The Goal: Blur the line between learning and working.
At last comes the final ascent: rope teams, technical gear, and professionals guiding the climb. Traditional internships have a fundamental flaw. They're time-bound windows that are hard to access. A lucky few get summer internships. The rest graduate with no real-world experience.
We're building something different. A persistent professional environment where students can contribute at any level, from tiny tasks to full development roles, and grow at their own pace.
Endless works with independent game studios where professionals and advanced students work side by side. Pros get motivated, skilled collaborators. Students get mentorship, portfolio pieces, and pathways to paid work.
Some games are generated by professional studios we partner with, like E-Line Media. Others bubble up from the community. A capstone project that shows promise gets support to go commercial. A community game that gains traction gets professional polish. The line between "student work" and "professional work" dissolves.
My expectation is that over time, the community will generate far more creative ideas than professional studios ever will. The risk-taking that comes from a small group with an innovative idea unlocks mechanics a big studio might not discover. And the creativity of thousands of contributors will dwarf what any single studio can imagine.
Like open-source software, contributors range from occasional bug-fixers to core developers. In games, a student might start by designing a single level, graduate to implementing features, and eventually join the professional team with a job. All while learning at their own pace. Imagine continuous access to an internship, where there are always studios to plug into.
Portfolios grow from shipped features. Standouts graduate into paid roles.
In effect, Endless works as a publisher. We finance development, coordinate marketing and distribution, provide ongoing support, and manage IP rights. This publishing arm allows small studios to bubble up within the community and commercialize their games.
We're also an incubator. A capstone team that wants to turn their project into a company? We can help. Mentorship, connections, sometimes capital. The goal is a vibrant ecosystem where games can start small and grow as more people join.
The jump to professional standards is steep. In Phase 4, your teammates forgive rough edges. In Phase 5, the bar is higher. Code needs to be clean. Art needs to hit the style guide. Deadlines are real. Missing one affects the whole team.
The second struggle: professional communication. Writing clear bug reports. Giving critical feedback tactfully. Receiving criticism without defensiveness. These soft skills matter as much as technical skills, and they're harder to teach.
Some students aren't ready. They try, they struggle, they retreat to Phase 3 or 4 to build more skills. That's fine. The opportunity remains open. This final phase completes the cycle, from learning through play, to making games, to working professionally in games. It's not preparation for industry. It's a bridge into the workforce.
This is Phase 5: Work with professionals. Get paid. Learn to be a professional.
These five phases aren't discrete steps. They overlap. The journey should feel continuous. If you like what you're doing, you just keep going and naturally evolve.
You can also enter anywhere. A college student with coding experience might skip Phase 1 and enter at Phase 2. A game jam veteran might jump straight to Phase 3. A professional looking to mentor might enter at Phase 5. The phases aren't gates. They're descriptive, not prescriptive.
Endstar games and Threadbare become a draw to step inside of a Launchpad. Launchpads end with collaborative game-making. Community games teach the specialized skills needed for capstones. Students who've contributed in this community naturally form teams for capstones. The best capstone students are invited to work within professional game studios, and one day may become one of those professional game studios inviting more students into their studio.
Not everyone takes the same path. Enter wherever you like. Go wherever you want.
Why This Works
The single best way to learn to build software is to build software on a real team. No course, no bootcamp, no classroom can ever replace the lessons of code reviews, creative conflicts, sprint planning and shipping deadlines. Every recent college graduate will tell you the same thing: college didn't prepare them for their first job. The first job is learned on the job. So we asked: What if we could give students that "first job" experience while they're still learning? What if the learning environment was the job environment?
That's Endless Studios. A place where amateurs work alongside professionals. Where learning and working are the same activity. Where you can start as a complete beginner and, if you choose, progress all the way to professional employment without ever leaving the mountain.
Right now, becoming a professional requires access to expensive education, to equipment, to internships, to networks. Most of the world's youth don't have that access. We're building a pathway that anyone can walk. Play. From there, every phase takes you deeper. You learn by doing. You progress by shipping. You get paid when your work has value.
This isn't charity. This is a scalable model. Professionals benefit from contributors. Contributors gain skills and income. Great games get built. The ecosystem is self-reinforcing.
Game-making is the most engaging and multidisciplinary pathway to the digital economy. It teaches skills transferable to any industry. Our students graduate ready to work anywhere. Community is where learning compounds. Where beginners learn from experts, contributors learn from feedback, and everyone learns by shipping together at scale. We simply put those two insights together: the power of community and the power of games. Building the skills to thrive in the modern workforce is a monumental effort. For a young person, it's the work of a lifetime. Yet today, there is no meaningful way to experience the workforce before entering it. Not at scale. Not at depth. There must be.
If we want an entire generation to reach the peak of their potential, we must build paths that guide them every step of the way. From those early days when they need encouragement to those later years when they need to learn to love the sweat and the heat. From the days when mentorship looks like gentle teaching to the days when it looks like telling them their work isn't ready to ship. From coddling to chiseling. From the fire of passion to fire that forges strength.
This is our way of doing that.
We hope the world will build more paths like this. But in the meantime, we invite you to join us on this journey to the top of the mountain.