So I come from a background of Civil Engineering. We basically don't do ANYthing arbitrarily. There's a reason for basically every aspect of a design. Sometim

So I come from a background of Civil Engineering. We basically don't do ANYthing arbitrarily. There's a reason for basically every aspect of a design. Sometimes there are competing criteria that leave it to humans to decide, but honestly it's rare. Usually the constraints drive the design from concept down to minute details. Within the constraints and criteria, there's codes and manuals that cover almost everything. It's always seemed to me that software has really suffered from a lack of this approach. Is it the best way to maximize innovation? No, but in some ways, you might be surprised how much placing heavy constraints on a project will drive innovation.