There’s a point in every game developer’s journey where the problem stops being “I don’t have enough time.”

You actually have time. You just don’t have the energy.

I’ve struggled with this myself, especially when trying to build games around a full-time job and everything else life demands.

And I eventually realized that the way I was approaching game development was part of the problem.

There’s a different way to think about making progress when you’re exhausted.

I explore that idea in my new video, and I think it might change the way you look at your own game development routine.

The interesting part is what happens when you stop trying to build the whole game...

What if finishing your game isn't actually the goal?

One of the biggest lessons I've learned in game development is that making a game and building a path in the gaming industry are two different things. You can spend years developing something technically great, but if nobody knows about it, supports it, or gives you feedback along the way, the launch can feel very different from what you imagined.

The shift is to build your community alongside your game. Share the process, listen to feedback, and let people become part of the journey. That's how one project can become the foundation for the next one, and eventually for a real career in game development.

I explore this idea in my latest video, The Real Reason Most Game Developers Never Make It.

I'd love to know what you think. Are you building just a game, or are you building a path around it?

#GameDevelopment #IndieGameDev #GameDev #GameCreator #IndieDev

Getting into game development isn't about finding the fastest path. It's about making sure the time you're investing is actually taking you in the right direction.

In this video, I talk about what it really takes to start building a career in the gaming industry, why focusing only on getting hired can put you in the wrong mindset, and why creating meaningful projects and sharing your progress can create opportunities over time.

I also share some lessons from my own journey, including mistakes I made early in my career, why I chose Unreal, and how consistently building and sharing my work helped me create more opportunities and independence.

If you're trying to figure out how to turn your passion for game development into a real career, this video is for you.

Watch the full video and let me know what you think.

For a long time, I thought becoming a game developer meant leaving behind the life I had already built.

I had a successful company, a family, and a life that was working. But there was still this feeling that I wanted to create something different, something that had a deeper meaning for me.

The journey into game development didn't happen overnight. Moving to Canada was one major change, and then figuring out how to build a career in games became another.

I made a lot of mistakes along the way. I chose tools that weren't right for what I wanted to create, worked on projects that never received funding, changed direction several times, and had to figure out many things without having a mentor to guide me.

Looking back, I don't regret those experiences. They helped me understand what I actually wanted to build and, perhaps more importantly, what kind of person I wanted to become through the process.

That's a big part of why I'm building this community today.

I know what it's like to have the desire to create games but not really know which direction to take. I know what it's like to feel stuck, to keep starting again, and to wonder whether you're making the right decisions.

I had to figure out a lot of that on my own.

If I can make that journey a little clearer for someone else, then the difficult parts were worth it.

That's also why this Patreon community matters to me. You're not just supporting a YouTube channel. You're helping me continue creating games, sharing what I'm learning, and building a place where aspiring game creators can find guidance and encouragement along the way.

And I'm very grateful to have you here.

I also put together a video about the journey that brought me here, from leaving my previous life behind to finding my way into game development.

Thank you for being part of the journey. We're still building.

A good partner can multiply what you’re capable of building. The wrong one can quietly drain the momentum out of your dream.

This is a topic I wanted to talk about because it comes directly from experience. Throughout my career, I’ve had partnerships that helped me grow tremendously, and others that cost me time, energy, focus, and equity. Looking back, the biggest lesson wasn’t that partnerships are good or bad. It was realizing that you shouldn’t look for a partner simply because you don’t want to build alone.

Sometimes starting alone is exactly what helps you understand what kind of person you actually need. You begin to discover where your strengths are, which responsibilities are consuming your time, and what areas are holding the project back. That experience gives you a much clearer picture of the person who could genuinely expand what you’re capable of doing instead of simply duplicating your skills.

For me, that distinction matters more than ever. If I’m already focused on development and technology, I probably don’t need another person doing exactly the same thing. I may need someone who can help grow the community, communicate the vision, create content, or take ownership of the areas that allow the entire project to move faster. A strong partnership is not just about sharing the same interests. It is about bringing together strengths that make the whole thing more capable.

But skills alone are not enough. Commitment reveals itself through execution, and that usually takes time to see. Everyone can be excited during the first conversations, especially when the idea is new and the possibilities feel endless. The real test comes later, when progress becomes difficult, when you are working after hours, when problems appear, and when nobody is there to tell either person what needs to happen next.

That is when you discover whether someone pushes alongside you or whether you have to keep pulling them forward.

In this new video, I share some of the partnerships that shaped my career, the mistakes I made, the warning signs I would take much more seriously today, and the questions I believe every aspiring studio founder should ask before sharing ownership of what they are building.

I’d especially love to hear your perspective as part of this community. If you were building a game studio today, would you rather begin alone or build it with a partner? And if you chose a partner, what would that person need to bring that you don’t already have?

#GameDevelopment #GameDev #IndieGameDev #GameDeveloper #GameStudio #IndieDeveloper #UnrealEngine

Why do so many aspiring game developers start with a great idea, spend months learning, and still never finish the game they wanted to create?

In this new podcast episode, I wanted to step away from the technical side of game development and talk about something that I believe has an even bigger impact on whether you actually move forward: the way you approach the journey itself.

Over the years, both from my own experience and from talking with other developers, I’ve noticed four traps that repeatedly appear: the scope trap, isolation, tutorial hell, and identity mismatch. None of them are really about whether you know enough Unreal Engine, C++, Blueprints, or any other technology. They are about how you structure your goals, how you learn, how you share your work, and ultimately how seriously you treat the future you are trying to build.

One of the biggest mistakes is going to either extreme with scope. You can create projects so small that they never represent the kind of developer you want to become, or you can attempt something so ambitious that finishing it becomes almost impossible. The goal is to find that middle ground: create something meaningful and impactful, but build it through a realistic architecture and a clear sequence of mechanics.

Then there is isolation. Many of us start game development after work, alone in a room, with nobody expecting a delivery and nobody checking our progress. That freedom can be wonderful, but it can also make it incredibly easy to lose direction. Sharing what you create changes that. You get feedback, you begin building an audience, and suddenly the project is no longer something that exists only on your computer.

The third trap is something almost every developer knows: tutorial hell. You finish one course, then another, then another, waiting for the moment when you finally feel “ready.” But the goal should not be to learn everything. Learn the fundamentals, decide what experience you want to create, and then learn the specific knowledge required to build the next part of that experience.

The last one may be the most important: identity mismatch. If game development is something you genuinely want to turn into part of your future, at some point you have to stop treating it only as something you do when you happen to have free time. You begin approaching it with the mindset of someone building something meaningful, investing today in the person and creator you want to become tomorrow.

Toward the end of the episode, I turn these four traps into practical actions you can start applying immediately: define the game you actually want to create, build and share consistently, learn according to the needs of your project instead of endlessly consuming tutorials, and start treating your creative path as an investment in your future.

I’d really like to hear your perspective on this one.

Which of these four traps has affected you the most: scope, isolation, tutorial hell, or mindset?

🎧 Watch or listen to the full episode and let me know in the comments. I think this could lead to a great conversation within our community.

#GameDevelopment #IndieGameDev #GameDev #UnrealEngine #GameDeveloper #GameCreatorAccelerator

I wanted to create video games when I was twelve years old, but I did not begin consistently building my professional path in the industry until I was around thirty-eight.

For a long time, it would have been easy to look at those years as time I had lost. I could have assumed that the people who started younger had already moved too far ahead, and that I had missed the ideal moment to begin.

But that is not how I see those years anymore.

Before entering game development seriously, I learned how to solve difficult problems, work with teams, adapt to new technologies, build businesses, manage pressure, and continue working when meaningful results took longer than expected. When I finally redirected my career toward games, that experience came with me.

I was not starting from zero.

That realization changed the way I think about the “perfect age” to become a game developer. Starting young can be an enormous advantage, but starting later can give you something different: a deeper understanding of responsibility, iteration, ownership, and what it actually means to commit to a difficult path.

However, experience does not automatically make someone ready. There is a mistake many experienced people make when they enter game development, and it can erase nearly every advantage they have built.

That mistake is one of the reasons I wanted to make this video.

The real question is not whether you are too old to begin. It is whether you have reached a point where you are prepared to protect your time, finish what you start, learn from disappointing results, and continue when the excitement disappears.

Sometimes the years that make you feel late are the same years that made you ready.

In this video, I share the three advantages that life experience can bring into game development, the danger experienced beginners often overlook, and three questions that can help you determine whether you are truly prepared to build this path.

Watch the full video!

I would also like to hear your story. How old were you when you first imagined creating games, and what is motivating you to pursue that path now?

I gave Claude Code access to an Unreal Engine project. The first result looked like a success.

The code compiled, the gameplay cycle worked, and I reached a functional prototype much faster than I expected. From the outside, it was exactly the kind of result that makes AI-assisted development feel incredibly promising.

But once I started examining how the system had been built, the experiment became much more interesting.

One decision in particular forced me to question whether the project was truly moving forward or whether the working result was hiding a problem that would only become visible later.

That moment changed the way I think about using AI inside Unreal Engine. It also made me reconsider when AI genuinely saves time, when manual work is still the better choice, and what developers need to understand before trusting an AI-generated solution.

I explore the full experiment and what I discovered in the new video.

After watching, I would love to hear how you are currently using AI in your own development process. Are you using it mainly for code, debugging, research, learning, or something else?

Lowering the bar sounds like the wrong advice for anyone trying to create an extraordinary game.

When I first encountered the idea, I resisted it. I believed ambitious creators should expect more from themselves, push harder, and refuse to settle. Lowering the bar sounded like an excuse to reduce the quality of the work or abandon part of the original vision.

But I was misunderstanding the idea.

There is a point where ambition stops helping us move forward and begins making every development session feel like a test we are failing. We can work for hours, solve difficult problems, and still walk away feeling as though nothing meaningful was accomplished. When that happens repeatedly, we often blame our discipline, talent, or lack of time.

What if none of those things is the real problem?

That question became the foundation of my latest video. It explores a specific place where many developers set the bar too high, and why changing that expectation does not require shrinking the game they ultimately want to create.

I wanted to share this with the Patreon community because many of us are pursuing meaningful creative goals alongside work, family, financial responsibilities, and ordinary life. A development plan that only works during perfect weeks is not a plan we can trust for very long.

The answer is not always to push harder. Sometimes the more ambitious decision is to reconsider what we are demanding from ourselves next.

After watching, I would love to hear your honest reaction. Does the idea of lowering the bar feel practical, or does part of you still resist it?

Being able to become a game developer does not automatically mean you should become one.

That is the question I explore in this new video.

Many aspiring developers focus on learning tools, completing courses, earning certifications, and building projects. Those steps matter, but they are only part of the journey.

The certification shows what you studied. Your work shows what you can contribute.

Many talented newcomers learn, create, and even share their progress, but their projects never develop enough direction or quality to create a meaningful reaction. They stay busy without building toward something people can remember. That is where the “wow effect” becomes important.

The wow effect is not about producing a complete AAA-quality game overnight. It is about steadily creating work that demonstrates growth, vision, quality, and potential. Every mechanic, environment, prototype, and system should become part of a larger direction.

When that direction becomes visible, people begin paying attention. Recruiters can recognize your potential. Other developers can see how you might contribute. Players can begin believing in what you are building.

But reaching that point has a price.

It requires discipline, patience, feedback, iteration, and the willingness to continue when your work receives little attention. It may require rebuilding systems, abandoning ideas, and spending months improving something before anyone notices.

So the real question is not simply whether you enjoy video games.

It is whether you are prepared to create them, solve the problems involved, share your progress, and keep improving until your work becomes impossible to ignore.

Watch the new video. After watching, I would love to hear your answer:

Do you believe game development is the right path for you, and what are you currently building to prove it?

If you are trying to build a serious path into game development while managing a job, family, and other responsibilities, I created a free training to help you understand the process and identify what may be holding you back.

Watch the free Game Creator Accelerator training

The Game Creator Accelerator is my lifetime mentorship program for people who want to build a serious path into the gaming industry while continuing to manage their job, family, and other responsibilities.

You receive ongoing guidance, weekly Q&A sessions, individual project reviews, accountability, and access to a community focused on helping you create stronger work, share your progress, and continue moving forward.

If this episode connected with where you are right now, you can learn more about the program here:

Learn more about the Game Creator Accelerator