Quote:
Originally Posted by sanddrag
Potential reasons:
1. Because they don't have someone who understands Physics leading the design.
2. Because they don't read Chief Delphi
3. Because they are ignorant of the world around them.
|
Wow,
I didn't realize that you could be wrong three times with three bullets. I don't mean this to be harsh, but here is where you are wrong.
1. my kids understand physics. Since that's what I teach, I make it my mission to sneak it in when I can.
2. I read CD as well as a few other members of the team. I'm not quite sure what was meant by this statement. We should all take the best ideas and use them as our own? Wouldn't that make this whole process so VERY boring? Yeah, I pointed out the "one day minibot" to my team today. They thought it was very cool but is beyond our ability to make (the most complex machining tool we have is a drill press). They want to focus on a consistent deployment system after watching 3 weeks of events. To sum up the mood of the team: getting a 4 sec minibot up the poll every match >> 2 sec minibot up the poll 80% of the time.
3. ignorant is such a "large" word to use. I'm not sure how to respond to that, so I won't.
Some teams want the students to learn something along the way (i'm not saying you don't Sand). FIRST gave them the problem. They are the ones who are deciding how they chose to solve the problem. I can point out the mistakes and help them along the way, but I refuse to do it for them.
I think it comes down to how you want to inspire your team. I have my way, other mentors have different ones. Who knows which is best. I don't. I don't think anyone truly can. What I can say is there isn't one correct way to do anything.