🧠 Learning 0
This is the first time I have opened this project in a long time (I've been working mainly at M2), and now I realize the importance of what everybody says about writing the code for the future's you. I understand some things, others seem silly, or I can even see that some code has clearly been written just because it was the first-fast workaround I have found. Not good. Not good at all.
Code must be written in such a way that it will continue to be understandable in the future, and not only that but also having a lot of precautions w/ the "solution" implemented. It cannot be a workaround. It must be a solution. It must be the best solution. Everything is better when I find a solution and afterwards find a way to enhance that solution further and further. Don't be lazy.
Why? Nicer code. Noob Pro code. Better code. That's what I aspire to.
🧠 Learning 1
Yes, this is a quite sneaky peaky UX improvement: so small that it is a (nearly but not totally) imperceptible change. However, it is not only good for the video I'll create about this game, but also a way of getting out of the comfort zone of having a lot of ideas but not taking them to action.
🐾 Steps