|
Re: [FTC]: FTC Software Requirements
Quote:
Originally Posted by Dave Scheck
I think that this is exactly what's needed. The code I ended up writing for teams was nothing more than a pre-made drive block that fit the style that they wanted. I don't see why a collection of these shouldn't be distributed to each competition as a safety net. Even better, the default code that comes on the controller should be available in a templated format. That way the teams don't have to change anything at their transmitter.
|
1st - What Iwrote last spring shold certainly be streamlined and otherwise improved. It worked, but it left a lot to be desired.
A better version of it would be useful as a teaching aid (allow teams to use it but not distribute the source?); but let's not forget that the students are supposed to learn how to give their machines software instructions...
Who has the right brilliant suggestion that stikes the correct balance between supporting learners and not rewarding sloth?
Blake
__________________
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 : 11-12-2007 at 23:08.
|