Why this blog?

-

Hi. My name is Behnam, and I'm a game developer. After some years of programming, I've found that I have a great interest in software architecture and anything that makes my life easier when developing a video game.

I've been following software architecture talks and tutorials for a few years. The reason I'm starting this blog at this time is that recently I realized things began to make more sense to me, and now I have something to share. Also, I want to crystalize my thoughts by writing about them, which helps me learn them better.

By sharing my knowledge here, I'm hoping that I can help other people to have an easier time developing video games by having a better architecture for their codebase. I'm also hoping to get feedback from other professional developers and improve myself.

The target audience of this blog is intermediate developers who can comfortably create small-size games but struggle with anything more significant than that.

I want to make it clear that in this blog, I'm not going to talk about HOWs but rather WHYs. For instance, I'm not going to talk about how to use the Unity ECS to create a million spinning boxes running at 60fps. But instead, I'm going to talk about why the Unity ECS can be a better architectural design for specific situations.

Comments

Post a Comment

Popular posts from this blog

Unity Project Folder Structure

-
Structuring our files in a Unity project can be challenging. In this post, I'm going to share my approach. There is no single method when it comes to structuring our files, but there is a single reason why we do so. I believe understanding this reason can help us a lot to choose the best method for a given scenario. Think of a situation where you have a few hundred files in a single folder. How difficult would it be to find a particular file among them? Pretty hard, right? Well, that's why we need to structure our files! We do so to make it easier to find them later. One approach is to subdivide the files and put them in subfolders based on their type, then their features. So we will have something like this: Project Scripts Player Movement.cs Attack.cs Enemy Pathfinder.cs Attack.cs Prefabs Player Character.prefab Weapon_A.prefab Weapon_B.prefab Enemy Dwarf.prefab Elf.prefab Materials Player Outfit.mat Weapon_A.mat Weapon_B.mat Enemy Dwarf.mat Elf.mat This approach works fine i
Read more

Implicit coupling will stab you in the back!

-
There are many ways to create implicit coupling in your game project, including the codebase. For example, if you copy-paste some logic in your code, that's an implicit coupling. The easiest way to spot this kind of coupling in your project is to ask yourself this question: "If I change this, do I also need to remember to change something else somewhere else?". If your answer is yes, then there is an implicit coupling between these different parts. The danger with implicit coupling is that it's not tracked by any system, such as a compiler; thus, we rely on the developer's memory or attention to maintain this relationship. The last thing we want to do in game development is to take away the developers' attention or fill their memories with unnecessary information. This reduces their productivity. Also, relying on the developers' memory or attention is not a reliable approach for game development. Humans often make errors, and this is the root of many nasty
Read more