> and have the same tiring conversations about naming conventions, logging, data consistency, validation, build scripts, etc. Sounds like bike-shedding to me.

> and have the same tiring conversations about naming conventions, logging, data consistency, validation, build scripts, etc. Sounds like bike-shedding to me. Eg. You start with solving trivial problems instead of the hard problems. Usually the first thing that is decided is what framework to use, often by a non technical person that herd from a friend that is was good. Rather then having the engineers sit down and think about what are the biggest challenges, and what is the best framework suited to solve the hardest problems.