3 ms·

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 perfectionning 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 perfectionning my work than actually do the work. I settled for two languages for the back (go and python and a fixed nr of libs) and one framework for the front (quasar, vue3, vite), and PWA to have an "app" on desktop and mobile. This is heavy, not optimized, ebery problem looks like a nail to my only tool (a hammer). But I write mostly for myself and managed to write over an evening the app which would track chores at home for the kids, display it on the home dashboard and disconnect their phones until they are not done (just kidding for the last one, my children are way stronger than me and I do not take risks, and stay with the "because I said so"). I have many similar apps, some I throw away, some I use, some I open source. Perfectionism is painful.

KronisLV 4y ago
> 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.
- satvikpendem 4y ago
  Yeah, I used to obsess over the best tool for the job too, but I realized I'm not actually getting anything done. I'd rather get something shipped and have it be somewhat shitty (like here where I'd initially not done any performance optimization but added it later) than to obsess over perfection and not have anything to show for it.

KronisLV 4y ago

> 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.

satvikpendem 4y ago
Yeah, I used to obsess over the best tool for the job too, but I realized I'm not actually getting anything done. I'd rather get something shipped and have it be somewhat shitty (like here where I'd initially not done any performance optimization but added it later) than to obsess over perfection and not have anything to show for it.