I am for sure not the first person in the world who decided to build a project in public. But as I did so many mistakes on my way (so far), it is something like a gift to others who suck at programming.
But jokes aside. My project already works quite well and I am going to tell you, how I did that. And of course we are going to see the good, the bad and the ugly.
What is it all about?
I will be creating a good ol' browser game with you. It's going to be called "dorfclubs", which loosely translates to "grassroots club". It will (hopefully) bring back the joy of the Anstoß-Series (well, let's not talk about the releases after Anstoß 3). And we are going to event-source the core of it.
Basically, every change of a server is written down to an event log. This log is an append-only log, so there is no such thing as "deleting". This gives the user the opportunity to travel in time. And we can perform statistics on those entries. And the most fun thing: We can even build statistics that we did not even think about right now. It basically is "remembering things". But on speed.
I decided to build in public to get more audience and make more money share the things I learned, make mistakes, learn from them (and probably repeat the exact same mistakes again).
The tech stack
In this series I am going to write a lot about different technologies. As a reader, you do not need to be an expert in any of these. I wouldn't hurt if you heart about NodeJs, VueJs, Nuxt, PHP, Laravel, Linux and Docker before. If you don't: Don't worry. We will go into the details later and Frameworks like Laravel and Nuxt are a great entry point to dive deep into a new language (not kidding, I mean it).
So... Sit back and relax. We will get started.
Roman
