|
Re: Open Invitation to help design a programming game for FRC
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.
|
By whom?
If you are the proverbial customer, you defined what the software must do and be. If adapting to unspecified conditions wasn't in your specification, the software isn't a failure.
If you aren't my customer, your opinion is interesting, but not particularly relevant or motivating, until it can be linked to something I or my customer require.
My guess is that a game or challenge that (mostly) matches what FRC is, instead of what someone says FRC should be, will have greater success.
On the other hand, anything that is both fun and easy to participate in stands a good chance of succeeding.
__________________
Blake Ross, For emailing me, in the verizon.net domain, I am blake
VRC Team Mentor, FTC volunteer, 5th Gear Developer, Husband, Father, Triangle Fraternity Alumnus (ky 76), U Ky BSEE, Tau Beta Pi, Eta Kappa Nu, Kentucky Colonel
Words/phrases  I avoid: basis, mitigate, leveraging, transitioning, impact (instead of affect/effect), facilitate, programmatic, problematic, issue (instead of problem), latency (instead of delay), dependency (instead of prerequisite), connectivity, usage & utilize (instead of use), downed, functionality, functional, power on, descore, alumni (instead of alumnus/alumna), the enterprise, methodology, nomenclature, form factor (instead of size or shape), competency, modality, provided(with), provision(ing), irregardless/irrespective, signage, colorized, pulsating, ideate
Last edited by gblake : 15-06-2015 at 01:27.
|