![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/0943eca5-c4c2-4d65-acc2-7e220598f99e.png)
2·
1 year agoThis guy thought about that question, if you wanted to see that perspective.
https://reducing-suffering.org/how-much-direct-suffering-is-caused-by-various-animal-foods/#Summary
This guy thought about that question, if you wanted to see that perspective.
https://reducing-suffering.org/how-much-direct-suffering-is-caused-by-various-animal-foods/#Summary
Why event organization? are you already familiar with each piece in that list? Why that tech stack? Do you need to care about scaling or is self hosting more fun for this?
The distinct concept might be to take that stack and do something else with scheduling? I think weaving in a thing you like or want to specialize in would be better than a generic scheduling app (I don’t know those apps you mentioned).
If you’re doing a web app focus then the MongoDB INSERTS and updates will be easy to template once you find how they communicate. The DB should do less of the logic and just hold your “primative” data that can’t be calculated. It might even do BLOBs if you want to skip a cloud bucket because you won’t have to scale…
Good luck!