Comment by davnicwil

> The tech stack would be simple too. At the time of planning, Svelte 3.0 was the new shiny so I decided to use it for my UI. I knew that I wanted to host everything on Netlify, so for the backend I'd write a couple serverless functions to present the questions and check the answers. The main list of nouns could be served from a static JSON file and, as I'd be the only user, I could safely persist previous quiz results and a high-score to local storage.

To be blunt this is exactly the kind of stack that you'll regret hard if you ever come back to pick up an abandoned project.

They always seem simple at the time when the whole system is loaded into your brain, but will be utterly incomprehensible on cold start in a year, especially when the cool stuff you stitched together has itself respectively moved on several major versions.

I've learned this the hard way from trying to revisit several abandoned projects over the years. Seriously, just use your language's equivalent of rails, and follow all the conventions. That way you can go right to the docs in future and pick up where you left off.