So, I'm starting a Game Dev blog

I’ve decided to start blogging about certain aspects of game development and design, not because I’m any sort of an expert; I’m really not. I want to start writing up my experiences as much for myself at a later date as for anyone else’s benefit. What I have found whilst I’ve been developing my first game is that I often get wrapped up in a single problem, figure out a suitable solution and then don’t come across the same problem for a long time. At that point, I have to go through the entire learning process again. If I can explain the issue and describe the solution then it’s a good indicator that I understood the problem well enough to help someone else, perhaps even myself at that future date. Ultimately, this investment in time is likely to save me in the long run.

The blog isn’t going to be in any particular order at first. I’ve completed the vast array of requirements that I wanted my current game to do so I’m now creating levels and that means having to go around that learning loop yet again to get each level to be consistent with my overall design and the test level I created.

The game has probably only taken a couple of months in working days to get where I have so far but spread over two and a half years. I typically only get to work on the game on Fridays and, for the past six months, I haven’t had time at all to invest in the game development because of my day job. So now that I’m coming back to it and I’m trying to get my head back into it I’m really finding my lack of documentation difficult to overcome. Hopefully, this blog will go some way towards rectifying that. If someone else gets something out of it then it’ll be extra rewarding.