Yep, I highly recommend going for not over-engineering things from the start. Use simple and quick’n’dirty where ever you can to keep momentum and not get bogged down into details. Especially early on in a project where it’s important to test ideas and game play and not code large and complex systems.
I had the privilege of working with the code for one of Bens games when we adapted it for release on Game Distribution (also on Poki and soon on Nintendo Switch). The simple approach taken by Ben makes it super easy for someone else (in this case me) to pick up the code and quickly make changes!