View Single Post
  #348   Spotlight this post!  
Unread 15-05-2013, 10:51
Nemo's Avatar
Nemo Nemo is offline
Team 967 Mentor
AKA: Dan Niemitalo
FRC #0967 (Iron Lions)
Team Role: Coach
 
Join Date: Nov 2009
Rookie Year: 2009
Location: Iowa
Posts: 803
Nemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond reputeNemo has a reputation beyond repute
Re: The 6 Week Build Season and 'Mentor Burnout'

An interesting thing about this thread: usually when somebody says "our team can't do xyz," people tell them to go out and find a way to do it anyway (recruit more sponsors and mentors, work in the offseason, etc). People jump all over that type of thing. But when a team says "we can't stop ourselves from overworking," there are more people agreeing than criticizing the "I can't" claim. I've already been critical of that, so I'll just say that I experience the same problem to a degree and empathize.

The people posting are largely a bunch of overachievers and people who, when told "you can't do that," will go out and figure out a way to do it out of spite. The overachieving culture is a big reason why so many teams bite off too much in their design process and end up not finishing the robot properly. Maybe this is something all of us should think about more when we decide our overall approach to an FRC season, whatever the length. Our ambitious, overachieving selves push us to make irrational decisions. That includes choosing fanciful robot strategies and choosing 7 day schedules for 20+ hours a week (or 30, 40...).

This thread has me dreaming of what we could accomplish in a longer build season, but I am also thinking about what I can do to make next year's 6.5 weeks more efficient and less stressful. It has been a very thought provoking thread.
Reply With Quote