|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: [FIRST EMAIL] Stop Build Day Survey
Quote:
The question FRC needs to ask itself is: Does it want to emphasize the engineering, including the trade-offs that are required (everything has a trade-off), or does it want to emphasize winning a competition? |
|
#2
|
||||
|
||||
|
Re: [FIRST EMAIL] Stop Build Day Survey
Quote:
I don't have the wisdom to know if eliminating bag day will negatively or positively impact those goals. My gut feel is it will provide more opportunities for teams to interact outside of competition which is a net positive to FIRST. The change to a district event structure actually emphasizes competition more than dropping bag day. (More matches... same money ... better use of resources is the theme presented.) Are districts overemphasizing competition? Food for thought. David |
|
#3
|
||||
|
||||
|
Re: [FIRST EMAIL] Stop Build Day Survey
I think these are two great points on this subject:
Quote:
Quote:
I think there are teams out there with a very low "ceiling" on their robots/teams performance that would not be solved with infinite amount of time available to them. This can be due to lack talent/resources/skill/capability/knowledge or whatever terminology you want to use. However, I think there is a much larger subset of teams that do have the knowledge/talent/capability to have a high "ceiling" but run out of time to realize the "ceiling" that they have. I get to watch a lot of the same teams in person at FIM districts and see a lot of the same teams from the first to second event. There are many that fall into the too little too late to make it into the DCMP. Many matches in the district system allows you to iterate and get better, with more time than regionals, but you still need to come out punching or you'll miss the DCMP boat. Believe me, been there, done that. I'm in favor of removing bag day because I see many teams reach their "ceiling" at their second event and be competitive, when they were barely able to perform at their first event. Also, removing should remove a level of bureaucracy with the sign in and out that is not value added IMO. People have shown to be very adaptive to the situation they were given. I don't think there will be the extreme cases of eliminating bag day will cause all the robots to be competitive, or it will burn all the mentors and students out. I just think it will help the middle tier teams reach their potential. To me, it's not that drastic of a change. |
|
#4
|
|||
|
|||
|
Re: [FIRST EMAIL] Stop Build Day Survey
This is kind of minor point but I haven't seen anyone make it.
Over 20+ years as an engineer in the semiconductor industry I have learned to appreciate good marketing requirements at the beginning of a project. There is nothing is worse than working on a project with shifting requirements and projects with really poor requirements have a habit of getting a lot of good engineers laid off. In FRC the equivalent to market requirements is the robot strategy that drives the build season. I would argue that consistently good teams are the teams that do the best job of predicting how the game is going to be played early in the build season. More build time and more chances to reset the design does de-emphasize this aspect of the program. |
|
#5
|
|||
|
|||
|
Re: [FIRST EMAIL] Stop Build Day Survey
Quote:
1) Yes, there are teams that, given an infinite amount of time will simply not be able to build a functional, let alone, competitive robot. 2) I'm not convinced of this. I'm convinced they run out of time because they think their ceiling is far higher than it realistically should be. 3) I think this is more an issue of teams needing to compete more. |
|
#6
|
|||
|
|||
|
Re: [FIRST EMAIL] Stop Build Day Survey
Quote:
No: The districts can be seen as allowing for the iterative process because you test your robot, then make changes. All engineering requires an iterative process. Yes: For the reasons you mention above, plus the goal of getting to DCMP. Personally, not only would I like to keep SBD, but I would like to get rid of the unbag times before the districts. Unbag times defeat the purpose of SBD. (Unbag times between events makes sense to fix things.) I've been on teams that went to regionals, champs, and districts. Districts are the same length of time as regionals (3 days), so why is there a different structure to the unbagging rules? It makes no sense to me. |
|
#7
|
||||
|
||||
|
Re: [FIRST EMAIL] Stop Build Day Survey
Quote:
Quote:
|
|
#8
|
||||
|
||||
|
Re: [FIRST EMAIL] Stop Build Day Survey
My one-liner - "I support tightening the current stop-build restrictions because I don't want to see the total FRC program slide too far down the slippery slope of over-emphasizing the competition part of an otherwise well-rounded spectrum of activities."
Something that I think fits into the topic(s) of some recent posts ... IMO, there is a tangible difference between inspiring someone to consider becoming a Scientist, Technologist, Engineer, or Mathematician (or whatever), and attempting to actually transform an inspired person into one of those. Like most/all of us, I love seeing students become better at STEM skills, but I also try to stay aware of the difference between creating the inspiration, and subsequently taking on responsibility for replacing the formal training available from other sources. Sure, you feed the STEM hunger of eager/inspired students, and you feed them as much as you and they can handle - because it's fun. But, while there is no doubt a lot of overlap between inspiration and subsequent training, the two things aren't interchangeable. When planning club/team activities, whenever we reached the point of having to choose/recommend how we are going to spend our chunks of scarce time, I try to think hard about whether I/we should invest those hours and energy into making an OK robot better, or into introducing new people to STEM opportunities. Those two things certainly aren't 100% mutually-exclusive, but they aren't 100% identical either; and the clock is a merciless taskmaster. Blake Last edited by gblake : 09-09-2016 at 13:21. |
|
#9
|
||||
|
||||
|
Re: [FIRST EMAIL] Stop Build Day Survey
Quote:
I'd rather extend that unbagging rule to regional teams than deny districts that option. We'll agree to disagree on that point. It's a good debate to have. However, the survey didn't address this middle ground that already exists within the district system. David |
|
#10
|
||||
|
||||
|
Re: [FIRST EMAIL] Stop Build Day Survey
Quote:
Why bag up the primary teaching tool at the point when we have the most mentor, student, and sponsor engagement of any other time of the year? |
|
#11
|
|||
|
|||
|
Re: [FIRST EMAIL] Stop Build Day Survey
Quote:
2. If you need to "win" because of sponsor donations, you need to reset in the sponsor's minds what this program is about. 3. Engineers have drop dead dates. When they don't meet those dates, there are stiff penalties, typically financial in nature. The lesson of a drop dead date seems to be getting lost on people these days. |
|
#12
|
||||
|
||||
|
Re: [FIRST EMAIL] Stop Build Day Survey
Yes FRC is supposed to at least resemble the real world of engineering and in the real world deadlines are common and in some cases there are penalties that can be financial in nature to the company and if the company has to pay up because that deadline was missed the person or persons who failed to meet that internal deadline are likely to come under the scrutiny of their boss.
|
|
#13
|
||||
|
||||
|
Re: [FIRST EMAIL] Stop Build Day Survey
Quote:
2. By "Sponsor engagement" I mean that I have the most material and financial resources available to me via sponsors than any other time of the year. None of our sponsors care much about how well we do at competitions. 3. A competition is just a better drop dead date to me. The consequences are more tangible. It's also not like I can't set my own deadlines for my students anyway. Last edited by jman4747 : 09-09-2016 at 16:28. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|