My personal advise: don’t waste time dicking around with a tech stack. Just write the code for your application as directly as possible. Write what’s important

My personal advise: don’t waste time dicking around with a tech stack. Just write the code for your application as directly as possible. Write what’s important first to make it work then incrementally add features. A tech stack is like a cookbook. Commercial cooks don’t dick around with cookbooks because if they ever want to make money they must be able to ship a product fast and scale their effort across multiple orders simultaneously. Cookbooks are written for a home user to slowly slave over a single entree as a cooking passion. Likewise a tech stack is for a corporate developer who has more time to burn and would rather dicking around with configuring things than making tough product decisions. Not investing in a tech stack will force you to question your basic assumptions of architecture so that you focus first on the areas most important to your application. That puts your product first. As the application grows refactor as necessary.