Ask HN: How do you overcome decision fatigue in software development?
A few mantras I try to use for this type of problem:<p>* There are no solutions, just tradeoffs. Don't think there's a perfect tech stack.<p>* Done is better than perfect. Velocity matters. This generally means pick something you know if delivery is important.<p>* Boring tech tends to be reliable. Things like PHP, Rails, Django, etc. These tools have been around a long time and ironed out the kinks. Lots of documentation and tooling to make your life easier. Odds are very low your new fancy idea has any requirements that boring tech can't deliver on. This counts for every layer of the stack (frontend, DB, OS, etc).<p>I think the most important thing to keep in mind is you'll never have a perfect solution and that's ok! Don't get fooled by all the hype from new technologies that try to make you feel inferior for using other tech.