|
Re: Mythical Six Week Build Season
Quote:
Originally Posted by marshall
At the risk of poking the bear...
Is it disingenuous to say to people that "these teams built these robots in just six weeks" when in fact it is often 10 or 12 weeks for many (not all) of the top teams?
I know that I've had more than one comment from a mentor that they didn't expect to invest more than 6 weeks into the FRC build season only to find out that they invest a lot more time.
EDIT: Changed a word.
|
If I understand you correctly, what you are writing about are some of the reasons I would love to see this thread morph a robust discussion of the extremely complex subject of how to have a true 6-week build season, even if what gets built in that period might not be *every* single thing a team takes to a competition.
Human nature, and North American culture, being what they are, I don't expect that will happen; but that doesn't mean I can't lean in the direction of a cultural change. 
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 : 19-11-2015 at 14:25.
|