Game Engine development

The topic of games engines is as broad as any other topic can be. Problems are ranging from platform specific implementations of a clock up to allowing a gameplay developer change entity data during a playthrough and see the results immediately.

Because of this broad spectrum, it's one of the better ways to really learn how to solve complex problems without spending too much time in one place. This is particularly hard because it happens regularly that to make a solution perfect, we spent too much time on it, and yet in the end, it's might still not be good enough.

The possibilities

Additional to just problem solving, it is almost required to also get some basic knowledge in multiple topics, for example: Rendering, Audio, Geometry, Multi-Threading and Synchronization, AI, Physics, Networking, and the list goes on...

One could find his new love for a particular field and continue to learn more about it, or just try to connect every element in this huge machine.

Whatever it is, it will result in knowledge that isn't available by just listening to others. Some things need to be experienced, to be understood.

Why am I doing it?

I've started working on game engines around 8 years ago, with at least three fresh starts. I love the endless problem solving that is part of such a project, there is no end. And that is for me exciting. Additionally, it was always a way for me to never stop learning. Especially with this project, as with every month and year that passes, I'm not restraining myself to what I know, but I also try to be up to date with new things that are happening around this topic. Be it a new C++ standard specification, a new render API or design pattern.

I don't know how much this project will grow in the end, but I don't think about it too much yet. I've started a journey that I want to continue until the very end.

I do however want to share it at this point, as it's time to learn new skills, which also includes project management. Cheers if you got all the way here :D