What to do?

One day you start a project, out of curiosity, to learn, to grow, and just because. What do you do once you’ve gotten everything you wanted out of it, when there’s nothing left for you to learn, your curiosity being satisfied, but the project not being finished?

In private projects this question can usually be ignored, you might be a little frustrated about the idea of trashing another project, but you got what you wanted out of it, so it’s fine. However, if a project went public and people expect you to continue, it’s getting harder. Do you disappoint them and stop? Do you keep going at a crawling speed because you have a hard time forcing yourself to work on it? Or do you pull through and get it done? Currently I find myself in that exact situation. It’s not the first time, but I struggle with an answer more than usual.

Continue reading →

My thoughts about Go

I’ve always liked C and its simplicity, but it’s kinda tedious to write bigger programs in it, which is why I’ve always refrained from doing so. It’s not even the memory management, it’s simple things, like working with strings, or the overhead you have for calling “methods”, animal_do_something(animal). In comes Go, the programming language by Google.

Continue reading →