Go to Post Meanwhile, it's water over the dam, spilled milk, etc. Let's drop the subject and get on with life. I am seeing people warming up their lawyerism, which is not a good thing when we are coming up on build season. - EricH [more]
Home
Go Back   Chief Delphi > FIRST > General Forum
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rating: Thread Rating: 3 votes, 5.00 average. Display Modes
Prev Previous Post   Next Post Next
  #14   Spotlight this post!  
Unread 19-01-2006, 14:12
generalbrando's Avatar
generalbrando generalbrando is offline
Build, Break, Repeat
AKA: Brandon Mensing
FRC #0246 (Overclocked)
Team Role: College Student
 
Join Date: Nov 2002
Rookie Year: 2001
Location: Boston, MA
Posts: 366
generalbrando is a splendid one to beholdgeneralbrando is a splendid one to beholdgeneralbrando is a splendid one to beholdgeneralbrando is a splendid one to beholdgeneralbrando is a splendid one to beholdgeneralbrando is a splendid one to beholdgeneralbrando is a splendid one to beholdgeneralbrando is a splendid one to behold
Send a message via AIM to generalbrando
Re: Sharing Designs

I think part of the complication of this subject has to do with the difference between engineering concepts and designs/strategies, so I've divided my comments:

I think all teams need to increase the frequency that they share engineering concepts. Concepts such as how to telescope tubes using a single cable/string or how to create a claw on an arm that doesn't change it's angle (two-bar linkage). Sharing these ideas barely stunts creativity because they are the solution to the common problems that arise in engineering designs. I think it's actually more likely to increase creativity because it gives teams/students more tools in their engineering toolchest to pull out and use on their designs. These concepts are often text-book, but that doesn't mean a high-school student is exposed to them or even has access to them which is in part why FIRST is such a great experience.

To sum it up, this is about the question "how does it work?" which is something well all thought before we smashed open our first alarm clocks to find the ticking answer.

That said, I think *designs/strategies* should stay with a team at least until competition. Now, I know I showed the world our prototype ball launcher, but the reality is that there was no more there than there was at the FIRST kick-off. We simply remade a softball launcher using kit parts and robot-legal materials to prove that kit parts would work. What I think should stay with the team is their brainstormed/tested design solution to a part of the game challenge (such as ball collecting/launching). And my argument for this is in line with many others - keep the solution out of your mind and your creativity will have to take over to solve the problem. And that creates a greater learning experience.

To sum this one up as well, it's about the question "why was it designed that way?" Why can take apart a keyboard and figure out how it works. But to understand why we have the QWERTY keyboard layout takes a lot of creativity and learning unless you have the answer handed to you (you know, in history books or online). You don't get the answer by taking about the keys and playing with the membranes and silicone!
__________________
Lead Mentor of Team #246, Boston University Academy and Boston University, Overclocked
www.burobotics.org

Reply With Quote
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 09:12.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi