|
Using an engineer just for paper work is an incredible waste of a valuable resource. This raises once again the old engineer vs non-engineer team debate. From Sandrag's post it is pretty clear which camp he's in.
Engineering is more than knowing how to design a gear box or lift or other element of the robot. It is also about managing the project and making sure it gets done on time and on budget. This is a skill that cannot be taught from a book. You must learn on the job.
At least one company I know sends young engineers out to unsuspecting FIRST teams so the engineer can learn this skill in the cheapest way possible. This company also usually sends money with the engineer, and from their point of view the few thousand they spend is worth not loosing millions on a screwed up program later.
While it is perfectly possible for a team to do well in competition without engineering help, part of the purpose of FIRST is to inspire some of you to become engineers. How can you be inspired if you do not understand what an engineer does, and how can you know what they do if you don't hang around one for a while?
I'd say get an engineer who can qualify and put him to work. You don't even know enough about what you don't know to understand how much you'll learn by doing so. If you're wise enough to be interested PM me and I'll see about some referals.
__________________
Christopher H Husmann, PE
"Who is John Galt?"
|