Quote:
Originally Posted by BitTwiddler
I'm beginning to see that now. Different teams look at different things in accordance with their team selection philosophy. Some look at scoring effectiveness and others look at more qualitative attributes to find the best match for their alliances. Team 1678 has a nice set of slides that discusses this important topic.
It's been quite an education so far.
|
Thanks for the compliment. If you can't find a link to our slides from last year, message me and I'll send them. I'll also get our website team to post links to the slides on our website
www.citruscircuits.org (as well as for other workshops). We also hope to post the videos (finally), which includes a portion on the most important step in your draft process--having a heated argument between two members of the strategy team!
We will be giving an updated session on this plus strategy at our Capital City Classic workshops Oct 23-25 during breaks and after competition. (We may have a webcast set up as well.) For teams in Northern California, even if you're not competing, we urge you to come (plus we'll have a couple of food trucks.)
Note that we also have several whitepapers up on our tablet-based scouting system on Chief Delphi. We strongly believe that a team should build the scouting system because it's a great programming opportunity and not too overwhelming. It's a good place to use your extra programmers and recruit students who are already programming Android and iOS.