http://www.chiefdelphi.com/forums/sh...326#post403326
"The point is that while having the abiltity to find information in a variety of reference sources is a useful skill, it does not replace a good, complete, fundamental knowledge of your subject material." - dlavery
I like this quote because it makes me remember my first FIRST year (last year), being a rookie programmer, and the team deciding to go with Mecanum wheels. Over the next two weeks, we went over the physics, trigonometry, and everything about how Mecanum wheels work, and created our own (albiet very rough) control algorithm.
This year, we referenced an article on omni-drives, but again, we went through with the programmers (all new to FIRST programming) and made sure everyone knew how the wheels worked, and created our own new algorithm.
Building up a "portfolio" of things you know how to do/build/control over the years is a important thing for our team and is something I think teams should do. Teams learn just like a person does, and saves "thoughts" through either documentation or passing of information from older members to newer members. (This is why I am making it a point of our new programmers to document the new Mecanum algorithm we developed.)