Cheers for this idea. I was just wondering when I should stop the prototyping 'hacks', and sit down to try doing things smarter. I have tackled the "MVP" of m

Cheers for this idea. I was just wondering when I should stop the prototyping 'hacks', and sit down to try doing things smarter. I have tackled the "MVP" of my problem, and I am still hacking away to get exactly what I need, but I am starting to think about the whole idea of 'technical debt'. I have enough code now that it is starting to not fit in my head. I am wondering if this is the inflection point for starting to optimize - maybe abstract the code enough that I can keep building and keep it all in my head at the same time...