Recently I was able to finish a working prototype for a tiny side project and I skipped a few things that I would have considered "the right way", like even a good code structure, it went well and you know what, at the end, my code was a bit better structured, it was closer to the "right way" than I thought, it works well and each time I works on it, it get a bit closer to the "right way".

It made me realize that the "right way" is also a question of circumstance. The "right way" exist for one thing, avoiding some kinds of issues, but a side project is often quite simple, and most of theses issues won't happen, you most likely won't gains anything doing theses, so is it really the "right way" then?

It was hard to write that badly at first, hell my server side code is still mostly a single file, but most of my code took only a few hours to write, it's so easy right now to just erase a part of it and make it better. The frontend is using React, and at first it was a single big component, again the wrong way, but that component did something and it was working. Once I got some duplication in it, well I moved some stuff to another component. I could have done that earlier, I knew I would have duplication there, but I would have lost time making another component if I had abandoned the project (and I would most likely have if I had done everything "the right way").

So yeah, I'll keep doing it that way for now, doing it the bad way until I actually need the right way.