[Whatever]

This is kind of minor point but I haven't seen anyone make it.

Over 20+ years as an engineer in the semiconductor industry I have learned to appreciate good marketing requirements at the beginning of a project. There is nothing is worse than working on a project with shifting requirements and projects with really poor requirements have a habit of getting a lot of good engineers laid off. In FRC the equivalent to market requirements is the robot strategy that drives the build season. I would argue that consistently good teams are the teams that do the best job of predicting how the game is going to be played early in the build season. More build time and more chances to reset the design does de-emphasize this aspect of the program.