When reading the post, I had the impression that OP has never worked on a large project and seen what it's like to iterate on an existing project to improve it incrementally by working on the critical questions that may only make small changes to the overall app / project. Instead they're always thinking about and working on the large decisions (that are more or less inconsequential in the big picture) that you need to make when starting a project from scratch. I saw one comment about "fear of missing out". I think it's more along the lines of "fear of making the wrong decision and not knowing how to fix it". "Fear of the unknown" maybe. I think it's a useful exercise to think about and work on your early-stage execution (ie. figuring out how you'll prep things for a project, and learning about and understanding the implications of those decisions), but without any experience executing on the later stages of a project, it won't do any good.
There are generally alot of questions that need to be answered early on in a project, but once you've committed you just need to be confident that your skills to architect the project will be solid enough that they will keep you out of trouble, and the code will be modular enough that if you do spot big mistakes you can easily fix them within the existing architecture, avoiding the need for a complete (or large-scale) rewrite.
There are generally alot of questions that need to be answered early on in a project, but once you've committed you just need to be confident that your skills to architect the project will be solid enough that they will keep you out of trouble, and the code will be modular enough that if you do spot big mistakes you can easily fix them within the existing architecture, avoiding the need for a complete (or large-scale) rewrite.