sounds like it just boils down to: try to choose the technology your team is familiar with, not what other teams are successful with Of course there's some bal

sounds like it just boils down to: try to choose the technology your team is familiar with, not what other teams are successful with Of course there's some balance needed. If your team is familiar with some niche language then long term that might not be a good strategy if you intend to bring more devs on board later. One side of this which I don't think is discussed often is the fun of choosing new technology. How do you balance having fun and being realistic at the same time? Fun meaning trying new technology, learning as you go, setting up systems that make you feel proud, etc. It can lead to failure, but I think having fun is important too.