Skip to main content

Why Am I YouTubing An Entire Game Development Project?

For a few weeks now I've been posting new episodes of a YouTube series I've been doing this month called Let's Make A Game. Now that I'm most of the way through the project, I wanted to think a bit about why I'm doing this, what I think people might get out of the videos, and what I hope to get out of it for myself. The best way I know to do that reflection is to write about it, and to share those thoughts.

So, Why am I YouTubing an entire game development project? Why would I put myself out there so publicly for anyone and everyone to look over my shoulder for twenty-five straight hours as I stumble, typo, and mistake my way through a skill I'm still learning and still very green on? And, why exactly would I think anyone cares enough to watch me code, mostly in silence, for twenty-five hours?

Why would anyone care to watch?

The truth is, I don't really expect anyone to. And that's okay. Part of this project required that I be okay with my own definition of success. So far, I have gotten some people watching the videos. I don't know if anyone will continue to watch more of them, and I'm positive that no one will watch all 25 episodes. But that's okay.

Maybe some people are just curious. Or, maybe someone will just be energized by the idea of someone doing this, even if they don't care to site through the whole thing. I'm sure everyone has better things to do with their time than watch me code for over a full day.

But, watching me code isn't actually the point.

Why do this when I'm not very good at it yet?

Because I'm trying to better. Of course, that's a very shortened answer. I hope that the process makes me better about scheduling. I want to practice this sort of video creation, because maybe I'll do more of it when I'm better at this in the future, and I want to know what I'm doing so I can produce semi-decent videos when they actually have good content.

Why do this in the first place?


The genesis of the project wasn't actually a desire to share any part of the process at all, though I consider that a fun plus. Instead, it was entirely for myself. I've been doing this One Game A Month thing for a few months now, the goal being to release one game a month of any quality or scope, and its gone well. But, I realized, I don't really know what's going into these projects. Sure I released one a month for about three months, but I don't know how much time I was actually working on each of them.

The episodic nature of the video series was a good opportunity to do one of these projects in a rigid time-box that I could track, document, and scope within to both practice and observe how I'm able to estimate what I can complete and what I can accomplish in a specific number of hours.

Hopefully this will feed back into my ability to plan these projects, and larger ones.

What's next? Will I do more?

I'm sure I'll do more video content about game development, but I'm just as sure that it won't be in this format. It has been very demanding, to be honest. Later, I might look at a series of Unity tip videos, for example. And in 2017 I hope to work on larger projects, putting a lot more time into them. But this video project has been a big time sink. I spend a lot more than an hour making each one-hour episode!

It has definitely been worth it, but I'm looking forward to wrapping it up.

If you found this post interesting, you can find all the episodes at my Let's Make A Game playlist.

Comments

Popular posts from this blog

On Pruning Your Passions

We live in a hobby-rich world. There is no shortage of pastimes to grow a passion for. There is a shortage of one thing: time to indulge those passions. If you're someone who pours your heart into that one thing that makes your life worthwhile, that's a great deal. But, what if you've got no shortage of interests that draw your attention and you realize you will never have the time for all of them?

If I look at all the things I'd love to do with my life as a rose bush I'm tending, I realize that careful pruning is essential for the best outcome. This is a hard lesson to learn, because it can mean cutting beautiful flowers and watching the petals fall to the ground to wither. It has to be done.

I have a full time job that takes a lot of my mental energy. I have a wife and a son and family time is very important in my house. I try to read more, and I want to keep up with new developments in my career, and I'm trying to make time for simple, intentional relaxing t…

The Insidiousness of The Slow Solution

In software development, slow solutions can be worse than no progress at all. I'll even say its usually worse and if you find yourself making slow progress on a problem, consider stopping while you're a head.

Its easy to see why fast progress is better: either you solve the problem or you prove a proposed solution wrong and find a better one. Even a total standstill in pushing forward on a task or a bug or a request can force you to seek out new information or a second opinion.

Slow solutions, on the other hand, is kind of sneaky. Its insidious. Slow solution is related the Sunk Cost Fallacy, but maybe worse. Slow solutions have you constantly dripping more of your time, energy, and hope into a path that's still unproven, constantly digging a hole. Slow solutions are deceptive, because they still do offer real progress. It is hard to justify abandoning it or trying another route, because it is "working", technically.

We tend to romanticize the late night hacking…

Why I Switched From Git to Microsoft OneDrive

I made the unexpected move with a string of recent projects to drop Git to sync between my different computers in favor of OneDrive, the file sync offering from Microsoft. Its like Dropbox, but "enterprise."

Feeling a little ashamed at what I previously would have scoffed at should I hear of it from another developer, I felt a little write up of the why and the experience could be a good idea. Now, I should emphasize that I'm not dropping Git for all my projects, just specific kinds of projects. I've been making this change in habit for projects that are just for me, not shared with anyone else. It has been especially helpful in projects I work on sporadically. More on why a little later.

So, what drove me away from Git, exactly?

On the smallest projects, like game jam hacks, I just wanted to code. I didn't want to think about revisions and commit messages. I didn't need branching or merges. I didn't even need to rollback to another version, ever. I just …