Quote:
Originally Posted by faust1706
Software is generally considered a failure if it fails to adapt to allow for an unforeseen, but plausible, use for the user.
For the most teams, their code cannot adapt. Their autonomous routine cannot adapt. The code fails to generalize across seasons.
|
If we want people to make adaptable code, we have to create a challenge that requires adaptability. If we want code to be generalized, we must design a challenge where modularity is a bigger advantage than the cost of the time taken to code it. FRC games are neither of these things. Doing these things definitely makes good code, but they aren't required for FRC. We can't compare the code we want submitted to what we think "should" be written for FRC. We have to make people do these things by showing the advantages of doing them, not berating people who don't.