View Single Post
  #82   Spotlight this post!  
Unread 01-04-2014, 20:25
Abhishek R Abhishek R is offline
Registered User
FRC #0624
Team Role: Alumni
 
Join Date: Mar 2013
Rookie Year: 2012
Location: Texas
Posts: 892
Abhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond repute
Re: Buyers' remorse / Pig in a poke

Quote:
Originally Posted by Daniel_LaFleur View Post
This is not a 'Pig in a poke'. When you signed up for FIRST, you knew you'd have random teammates. That is 'part of the challenge'. This is not a new rule from FIRST.

On the first day of competition you received your match schedule. If you did not go to each and every alliance partner (at a minimum) and MAKE SURE they could drive (drive train worked) and move during autonomous (just a few lines of code) and pin the ball for an assist, then you did yourself (and your alliance partners) a disservice. Helping to fix alliance partners BEFORE your match really helps this year.
Check, check, and check. But if you've been reading, teams have done this, and this year is different because you DO have to rely on your teammates to maximize points scoring, unlike last year, you're right. But what's to prevent the other alliance fom completely rolling over you due to a randomized schedule? The average team barely has the resources to manage their own robot. Now I'm hearing that if they want to win, they need to be bringing up all the other teams in their area, and then fixing mechanical and software issues for every one of their alliance partners at the regional. That's just spreading teams too thin.

To even further what I'm saying, we pretty much did exactly what you've been saying. But I would consider our team to be fortunate due to a relatively large base of members and experience.
__________________
2012 - 2015 : 624 CRyptonite
Team Website
Reply With Quote