|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: pic: Team 254 robot....almost there!
Congratulations on pioneering an amazing new way of approaching our competition. I have a feeling that a few years from now your two teams will be the answer to a FIRST trivia question. "Which two teams were the first to build the same robot?" Next year I'm sure many other teams will follow suit.
|
|
#2
|
||||||
|
||||||
|
Re: pic: Team 254 robot....almost there!
Quote:
|
|
#3
|
|||||
|
|||||
|
Re: pic: Team 254 robot....almost there!
Quote:
|
|
#4
|
||||
|
||||
|
Re: pic: Team 254 robot....almost there!
Collaboration is Great!
Kudos to you. I "real" life, several teams need to interact and share for the betterment of the business as a whole. Well done. |
|
#5
|
||||
|
||||
|
Re: pic: Team 254 robot....almost there!
That's a pretty scary but brilliant idea, in my personal opinion. So which one of you gets the credit for it?
Call me jaded, but FIRSTers are driven by awards and recognition. It's in our blood (though we don't like to admit it). What happens when both of you go after the same angle on your Chairman's application? Unless the rules change, only one of you can get the credit for it. True, if any team was to break the glass ceiling of "no teams beyond 200 have ever won the Chairmans Award", it would be 254...they definitely mirror the resources and support of a pre-200 team. But if one of you wins with it, the other team needs to find another angle to take next year, because that idea is now "old hat" to the judges. And knowing FIRST teams (for the most part), once an idea is recognized, all development on it ceases - because it has served its purpose. I think inter-team partnerships are great...I used to do it myself. But just as in those old movies with the business partner running off with all the money, things like that happen today, and a team who you thought you knew may not be one who you knew at all. And no, I'm not saying that against either of you in particular, you both are outstanding teams, I'm saying it because you just need to be sure you trust the team you're collaborating with. As for the collaboration aspect, I honestly would be terrified if all 16 Delphi teams had the same game design (or any multiple of teams, for that matter...I'm not just picking on Delphi ). Especially with their game experience, if everyone did this, it would stifle the rookie retention rate. I can absolutley see it turning into leagues of teams that "acquire" younger teams into their pipeline or shutting out teams that they didn't like. And I honestly don't want to see Dean take up an SEC role.Please don't get all upset about my viewpoint - it is only a viewpoint, and its not an angry one, just something from an old FIRSTer who's been through the trials and tribulations of collaboration and who cares about both of your teams. Last edited by Jessica Boucher : 16-02-2004 at 14:15. |
|
#6
|
|||||
|
|||||
|
Re: pic: Team 254 robot....almost there!
There are a few points here that need to be clarified.
First -- Yes, we did collaborate, and make the same robot. However, it is NOT the exact same robot. Each of our teams made small adjustments that the other did not. The robot is wired differently, and we will have different programs. We can't wait to see the Poofs at Nats and see what it comes down to. Who will win? Only strategy and driver skill will seperate us. Second -- I cannot think of a team that we could trust any more than the Cheesy Poofs. When they submit their Chairman's Award entry, I hope that they include our alliance. And we will do the same. I think that people are missing the point that we are acting as one team. If the Cheesy Poofs win an award for design, or for performance, or any other award, we can feel that we share it. We each worked on the other's robots, and we are each equally part of the alliance. On team 60, we're so close that we've become family. (Advisors, Machinists, Students, and Parents included) We've done so much together, that it is practically impossible not to be so close. We wanted to work with 254, who we consider an extended group of our family to show everyone what kind of collaboration is possible, when you're NOT worrying about "yourself" and "your own team's awards". Now we're working together to worry about "us" and "our team's achievements". Amanda M |
|
#7
|
||||
|
||||
|
Re: pic: Team 254 robot....almost there!
But you're not the same team. If you want to be considered as one team, then merge and register under the same number. I personally think that would be an innovative idea....teams working from different states to produce one robot...it seems to be more of what you both are going after. But until you merge, you are still in the competition's eyes as two separate teams, walking a fine line hand in hand.
Sometimes things may start out good, but then something happens that compromises that relationship. I've seen it happen too many times to think it won't happen this time, no matter how good you say your relationship is....and that's what I'm worried about...and it's something you both need to think about. |
|
#8
|
|||||
|
|||||
|
Re: pic: Team 254 robot....almost there!
im split on the idea...
i do like the idea that teams are forming together, and cooperating. however... i dont think its right to do what 60 and 254 did. i mean its kinda cheap. yuo have one team design half the robot, and the other team do the other half. there are teams who are running themselves ragged trying to accomplish a goal. the whole concept of FIRST is to have unique designs. and gauranteed, its a good way to promote first's unity. its bad that the two teams only have to do half the work. its kinda unfair, but what can you do, disqualify them? no because they broke no rule. however, i think it a kick to the chest for some teams. just my 2cents worth. |
|
#9
|
|||
|
|||
|
Re: pic: Team 254 robot....almost there!
Well done Team 60 & 254! I think what you have done is great. Having worked on projects that require input, collaboration, agreement and shared work from different locations on the map, I can honestly say this is no easy feat! Anyone that thinks of this as a "shortcut" is missing the entire picture. You have added a layer of complexity to an already complex, stress-filled project. The end results.... I'm sure 2 awesome robots, but more importantly, students that may tackle future projects/problems with a better understanding of cooperation and working towards a common goal. And in my opinion we can't get enough of those students in the work force fast enough!
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|