I am sorry for not writing in a while, but as the finish date for GSoC comes closer, everything has to be ready for the end. My mentor and I agreed that the PR sould be submitted around August 14th, so these last days my intention was to have as much functionality as possible in before the PR came, as I was sure that after that I would have to spend all the time I had fixing things that I either forgot or didn\u2019t know were broken in the first place.<\/p>\n\n\n\n\n\n\n\n
I am sorry for not writing in a while, but as the finish date for GSoC comes closer, everything has to be ready for the end. My mentor and I agreed that the PR sould be submitted around August 14th, so these last days my intention was to have as much functionality as possible in before the PR came, as I was sure that after that I would have to spend all the time I had fixing things that I either forgot or didn\u2019t know were broken in the first place.<\/p>\n\n\n\n
However, I didn\u2019t get to implement much, since a pesky error on my part had me using valgrind for three days, looking for the source of a heap corruption. Luckily I found it and fixed it right in time, and the engine was in at least a playable (albeit not complete) when the PR happened.<\/p>\n\n\n\n
On the morning of the 15th I submitted the PR, and by now I have received tons of excellent feedback, and have compiled a list of fixes<\/a> that need to happen. Thanks to everybody for pointing these things out that fast, so I can get to work right away \ud83d\ude42 <\/p>\n\n\n\n On a side note, I am planning on writing a postmortem once the GSoC is done, with some important lessons I learned during this experience, which will hopefuly be of some use to future me and anybody that comes after.<\/p>\n\n\n\n