As an engineer I respect the way you're deploying simplicity to achieve an advanced technology - durability over the long term. This is a principle I have tried and failed to explain to businesspeople. Every bit of complexity comes at a cost. Bugs are caused by features.
You perfectly articulate and ordered my so far unordered thoughts about hobby projects and over-engineered state management. Thanks for sharing!
I have a vocabulary website where I track all the interesting words I want to remember. Update the codebase like once every year, add a word about once a month and view the site at most once a day. Since I moved away from mariadb and just use a plain json file that gets loaded on each page-view, it feels so much simpler and easier to maintain.
As an engineer I respect the way you're deploying simplicity to achieve an advanced technology - durability over the long term. This is a principle I have tried and failed to explain to businesspeople. Every bit of complexity comes at a cost. Bugs are caused by features.
I have a similar project at skratchpad.xyz (https://github.com/lucasgonze/planck-scratchpad). In that project the user benefits of under-engineering are the point.
You perfectly articulate and ordered my so far unordered thoughts about hobby projects and over-engineered state management. Thanks for sharing!
I have a vocabulary website where I track all the interesting words I want to remember. Update the codebase like once every year, add a word about once a month and view the site at most once a day. Since I moved away from mariadb and just use a plain json file that gets loaded on each page-view, it feels so much simpler and easier to maintain.