|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
||||||
|
||||||
|
FRC Blog - My Bad Call
http://www.usfirst.org/roboticsprogr...og-My-Bad-Call
Quote:
|
|
#2
|
||||
|
||||
|
Re: FRC Blog - My Bad Call
Very very professionally handled by Frank, he took responsibility into his own hands and took blame for the mistakes that were made, glad to hear that this worked out for all parties involved.
|
|
#3
|
||||
|
||||
|
Re: FRC Blog - My Bad Call
Gotta love Frank being able to admit when he's wrong. Glad to see 1323 going to champs!
|
|
#4
|
||||
|
||||
|
Re: FRC Blog - My Bad Call
What am I going to do with all of these torches and pitchforks now?
|
|
#5
|
|||||
|
|||||
|
Re: FRC Blog - My Bad Call
Considering how everyone has the hair trigger sensitivity of Nitro Glycerin and what's at stake this week and down in St. Louis you can bet you'll get good use out of them pretty soon.
|
|
#6
|
||||
|
||||
|
Re: FRC Blog - My Bad Call
Buy low, sell high! I like it.
|
|
#7
|
||||
|
||||
|
Re: FRC Blog - My Bad Call
Sell them to an angry mob for premium prices.
|
|
#8
|
|||||
|
|||||
|
Re: FRC Blog - My Bad Call
Frank has a knack for addressing issues in a manner most directors/leaders/officials should emulate. I truly appreciate his openness and transparency. It speaks volumes of his character that he's willing to admit a mistake and find the most equitable solution given the circumstances.
|
|
#9
|
||||
|
||||
|
Re: FRC Blog - My Bad Call
+1 Frank. Always happy with the way he deals with situations.
|
|
#10
|
||||||
|
||||||
|
Re: FRC Blog - My Bad Call
Unsure how I feel about the Wild Card, as I would imagine a waitlisted team who hasn't been to the CMP since 2012 or earlier is now going to receive an email telling them they will have to wait longer for that opportunity. I'm also not sure how many other teams who believe they were in a similar, if less publicized, boat as 1323 will feel about that decision.
It is unquestionable, however, that 1323 is an outstanding team with a robot that is absolutely Championship worthy, and I know they will make the most out of the opportunity they have been given. Regardless of the Wild Card, +1 for Frank's public mea culpa and the changes to the coupon process. Now keep going! The larger, unresolved issue of this season remains, one that has impacted not only teams, but also many volunteers, and I would hope Frank and HQ are gearing up to address the issue in some meaningful, experience-improving fashion: Quote:
Last edited by Travis Hoffman : 08-04-2014 at 11:05. |
|
#11
|
|||||
|
|||||
|
Re: FRC Blog - My Bad Call
I don't know that i would say Frank was "wrong". He made the decision he made with the information that was available / given to him at the time. As it turns out, that information was not complete. During the event, he made the right decision with the wrong information (he thought the team wanted a back-up, then got repaired, and changed their mind).
Later, given new / more information, he changed his decision to reflect the actual situation. I think this is a great outcome. |
|
#12
|
|||
|
|||
|
Re: FRC Blog - My Bad Call
Several are wondering why Frank/FIRST have not addressed other seemingly similar situations publicly as has been done here.
While I have no specific 'inside' information regarding any of the situations, lets give Frank/FIRST/HQ the benefit of the doubt here. It is clear that when the situation lends itself, a public explanation such as today's is given and the resolution is a good one. It could be that circumstances around other situations are such that a public 'airing' of the situation and its resolution is not in the best interest when all affected parties are considered. That doesn't mean that a best case resolution hasn't been made in ways that are not made public. FIRST has had more transparency in recent times, but that does not mean they can always be fully transparent on all matters. The directly affected parties for such issues deserve to have their concerns considered and typically will communicate directly with FIRST. The rest of the FIRST community is not entitled to have all matters and their resolutions explained to them as doing so may compromise some confidential information or have other undesirable effects. In some cases, parties are asked not to discuss resolutions with others as part of the resolution. This is the way it works in the real world, folks. Again, I am in no way saying that anything like this HAS happened in any situation (I have no clue), just saying that hearing nothing doesn't always mean you can assume nothing has happened. If you are not a directly effected party, assume that you do not have all the facts and your conclusions are suspect. This was the case for some CD posters concerning the SVR issue, prior to Frank's blog post. Thank you Frank for all you do for FRC. |
|
#13
|
||||
|
||||
|
Re: FRC Blog - My Bad Call
Since there seems to be some lingering confusion on the Orlando situation I'm posting the link to the thread that has posts from 1902, 624, and 233.
http://www.chiefdelphi.com/forums/sh...127083&page=12 Judge for yourselves how similar or not the situation is compared with SVR. It seems in both situations Frank was asked to make a decision with incomplete or incorrect information. **EDIT** 233 is the only alliance member left who does not currently have a spot at Championship. (They were also the alliance captain of that #1 seed) Last edited by sbrierty : 08-04-2014 at 14:16. |
|
#14
|
||||
|
||||
|
Re: FRC Blog - My Bad Call
Truck Town Thunder, FRC Team 68, commends Frank for this demonstration of Gracious Professionalism. We look forward to earning a spot this year and hope they are in our Division at the FIRST Championships.
|
|
#15
|
|||
|
|||
|
Re: FRC Blog - My Bad Call
Couldn't have handled it better . A+.
(Puts away pitchfork) Last edited by AlecMataloni : 08-04-2014 at 10:39. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|