> every time I start I get overwhelmed with what stack I should use, and how to actually get a ‘real’ application out Decision paralysis is something I struggl

> every time I start I get overwhelmed with what stack I should use, and how to actually get a ‘real’ application out Decision paralysis is something I struggle with too. Being able to recognize it and move forward, instead of second guessing yourself, helps a lot. It's good to remember engineering is about making trade-offs. Every solution will have shortcomings. I've also found being strict about refactoring to be very useful. Don't solve problems before you need to. Don't write a function till you actually need it. Don't start with a complicated class structure, start with a some procedural code and naturally grow and refactor it. Don't try to start a project as if it were already 6 months old. Bit of a ramble myself, but I get it. Second guessing your technical decisions is just something we have to find strategies to work around. Doing that makes us better. Working on side projects is a fantastic way to do it too, so kudos!