Allways Begin with Design
This is an old article from 2012. I was a kid. I learned a lot since then, so please do think twice when taking advice from me as a kid.
Once again, I am unhappy with the structure of one of my projects. That usually happens, if I am trying to implement a new feature and realize I actually don’t know how to fit it in the rest of the code.
In this case I am revising EpicRay (my raycasting engine in Java).
So… why am I lacking structure? Once again I was too lazy to properly design a project before I start coding. So I am actually going to design EpicRay now properly.
What aims do I have in mind: I hope EpicRay to be a decent raycasting game engine. This will probably make it rather complex, so I will need some help. My thought was to open a public github repository and make my project open source, once it got somewhere.
So design is a crucial step to open source… I mean, just try to find developers wanting to contribute to a chaotic project, wont happen. Also, I am not totally sure, how far I will get with this plan. I am hoping I will actually make it as far as the open source project.
As soon as I created the design document, I will create a github repository, so people can help me polish it with comments and so on. If somebody is interested :)
This post was imported from tumblr.