View Single Post
  #80   Spotlight this post!  
Unread 11-04-2006, 19:52
KenWittlief KenWittlief is offline
.
no team
Team Role: Engineer
 
Join Date: Mar 2003
Location: Rochester, NY
Posts: 4,213
KenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond repute
Re: The Triplet Challenge

Quote:
Originally Posted by RogerR
if we followed this line of logic, much of the behaviour that is termed 'GP' would no longer be acceptable. no more loaning parts, tools, or skills to needy teams. no more shared machine shops or practice Fields. no more mentoring rookie teams. we'd go from 'co-opertition' to total competition. the truth is, collaboration has been going on for as far as i can remember (i.e. the 6 years i've been involved), just in varying degrees. whether we're giving away spare wheels, chasing bugs in the electrical system, or helping to program an autonomous mode, any time we help another team to become more competitive, are we not 'collaborating' with them?
no, you are not. The difference is the core engineering challenge. Here is an engineering problem to solve - YOU come up with the solution.

I can mentor your team and show you step by step how engineers take a problem through the complete design cycle, I can lend you computers and tools and shop time, give you access to my machinists and welder, show you how to hook up wires and program the control system - ALL without solving the design problem for you.

This thread has turned into a 100% collaboration vs 0% debate - I never took that position. The first post in this thread (in my opinion) took it too far by saying that (if necessary) give a new team a complete robot design and let them copy everything.

I dont think collaboration is a bad thing, esp if you have one team that is rich in mechanical engineers and has a big machine shop, and you have another team with nothing but electrical engineers and SW programmers - If there is a natural divide then YES work together.

But dont take it to extreems. Dont let it end up where one team is only doing one small part, and esp dont give a team a complete design to copy 100%.

That is where this thread started drawing flack and criticism - going too far to the extreem. There are drawbacks and tradeoffs and fairness issues when teams collaborate. When you take it to the extreem then the drawbacks outweigh the good you are attempting to accomplish.

Last edited by KenWittlief : 11-04-2006 at 20:14.
Reply With Quote