View Single Post
  #35   Spotlight this post!  
Unread 03-12-2013, 15:17
techhelpbb's Avatar
techhelpbb techhelpbb is offline
Registered User
FRC #0011 (MORT - Team 11)
Team Role: Mentor
 
Join Date: Nov 2010
Rookie Year: 1997
Location: New Jersey
Posts: 1,624
techhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond repute
Re: Robot in 3 Days : Feedback

The upside of the RI3D build is that you can get a feel for any surprises with the game components without having to expend that energy yourself.

I can certainly see how teams might not have tunnel vision as much as limited resources to mess around and find their own way.

There's a saying among hackers: code wins arguments

If your team is hyper-focusing on the RI3D design then your team should take a good review of how that happens internally. There are many reasons why any team will just accept a solution. This is not to say that the RI3D design is flawed in any way but part of being an engineer is to be able to speak up against detractors and also to be able to accept that there may be problems with what you advocate as well. How one does that is often an art and a significant effort. Wrap that up in some politics and sometimes the best idea is just not the one everyone agrees on. Whatever the reason for the design choices one should not hold accountable the people that give their ideas away for basically free. The right way to work out a design is not by censoring potentially valuable information from the design process. That's a political fix that covers a fault somewhere in the process.

Last edited by techhelpbb : 03-12-2013 at 15:21.
Reply With Quote