> I am an amateur dev and used to look for the MOFD (most optimal framework of the day). > I realized that I spent more time perfecting my work than actually d

> I am an amateur dev and used to look for the MOFD (most optimal framework of the day). > I realized that I spent more time perfecting my work than actually do the work. > Perfectionism is painful. This mirrors my own experience, I actually wrote a bit more about it on my blog, albeit perhaps in the context of writing software that's actually maintainable "How boring or novel should your technology choices be": https://blog.kronis.dev/articles/how-boring-or-novel-should-your-technology-choices-be https://blog.kronis.dev/articles/how-boring-or-novel-should-... There are options out there that are kind of not very exciting, but have good documentation, tutorials to do most of the typical stuff, answers to most of the common problems and decent performance as well as the ability to scale. I also recently wrote a system to process millions of documents on a single node based on PostgreSQL, Java and MinIO as an exploratory project (to also explore things like database partitioning), it worked pretty well and I did that in a few evenings "Pidgeot: a system for millions of documents": https://blog.kronis.dev/tutorials/1-4-pidgeot-a-system-for-millions-of-documents-the-data https://blog.kronis.dev/tutorials/1-4-pidgeot-a-system-for-m... I guess at the end of the day you just have to pick something that works, maybe a bit on the boring side and stick with it as long as it's the right tool for the job.