Inkie Beard

This is a public shaming. No quarter will be given, no merciful anonymity or private repo's will suffice to hide my transgressions. I wrote a large complex recursive piece of functionality that was all but absent of documentation! At the time everything seemed so simple, so straight forward. I thought anyone on my team could open up the code, read a few small lines and instantly understand what was happening, even first thing on a Monday morning before coffee. Or so I thought.  Now fast forward to me on hump day last week, several months after writing that functionality. "That thing I wrote a few months back, it'll be perfect! Might need one or two miniature tweaks, should be simple", what an idiot. Should be simple - never utter those words! For all that you hold dear will turn to ash. Code that is as tight as the vaults of Fort Knox will turn to spaghetti riddled with bugs, like a scrap of peanut butter & jam sandwich consumed ants at a picnic. So much as whisp...

I've been thinking about, tinkering with and procrastinating over making a game for years. I have untold gigs worth of Unity projects clogging up, not only my desktop & laptop hard drives, but also our network storage drives! I sat down to do some serious thinking at the start of this decade and realised, the main reason I so often don't follow through (or get anywhere near even alpha stage) is because there is no actual story or driving idea behind my projects. Every few months I sit down to make a game. Once my prototype goes beyond the most bare bones mechanic, I eject like a boulder from a trebuchet. That or I spend several great night's working on getting a level designed, only to realise I have absolutely no clue what I'm going to do with it! This time it's different! This time, I have an idea. An idea based on a game that has already been made and works really well. Yes that's right, I want to make a game very similar to and inspired by one that a...

Is this thing on...?