|
Re: Open Invitation to help design a programming game for FRC
Quote:
Originally Posted by tindleroot
I know my team does not try to write generalized code, rather we practically start from scratch each year.
|
See previous posts in this thread. In general, you are supposed to start from scratch, unless you are legitimately attempting to publish something other teams will find useful.
That said, attempting to build a modest level of flexibility/generality into your code will probably (but not necessarily) help your team satisfy the requirements they impose on their producton processes and on the robots they produce; and writing some advice/examples along those lines into your team's training materials for future programmers, is probably a good idea.
__________________
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
|