Software Engineer (The one with 15 tabs of documentation open)
I’ve always wanted to make games when I was a kid. Going on the family laptop and searching “how to make a video game” and coming across a variety of results eventually ended up in me learning to program.
A couple really strangely programmed text adventures later, I started learning about game engines, and graphical languages, scripting and stumbling my way to be somewhat proficient.
Bachelor of Computer Science(Major: Software Engineering)
Attends local Hackathons
I make art, animation, sound, and design for my games. All assets in my games are made by me.
If you’d like to take a look at my code, have a look…
Tactical RPG in the vein of X-Com and Fire Emblem. Updated Weekly
I’ve long passed the stage of looking up code issues on stack overflow, and now stuck reading through obscure documentation when things go wrong.
Worse case I will “Monkeys on a typewriter” it until I get something that works, or atleast a little Shakespeare.
“Programmers were so preoccupied with whether or not they could that they didn’t stop to think if they should.” Is a common problem in many projects.
With real world experience of both very smooth development cycles and absolute dumpster fires, I’m always ready with a pre-emptive fire extinguisher.
I’m more than happy to just make software, but there’s always much much more when it comes to making software.
Researching technologies, buying and setting up servers, making sure we have a decent mode of communication is all essential.