Re: Rookie Questions
 

http://www.chiefdelphi.com/forums/sh...ghlight=manual

is a great resource to help search the manual for specific questions.

Email is a hard medium of communication sometimes. "Tones" can be misinterpreted, often when one is in a hurry. It happens to me all the time, and I end up saying "I'm sorry" at least once every day.
It's a new day. Let perceived slights and miscommunication go; and let's all try to be a little more gentle with each other. I've also learned many times that the old adage "if you don't have something nice (or helpful) to say, then don't say it." Just let it go and move on to the next thing in your busy lives. Sometimes what makes you feel better, makes the others feel pretty crappy.

Think before you press that "post quick reply" button. It really should read "post a thoughtful reply " button.

This is supposed to be hard work AND fun. Let's get on with the fun part.
I wish you all well and hope those designs are getting nailed down on paper (or CAD or whatever) in the near future.
p.s. this is what my old team would have called the "mom-talk."

Re: Rookie Questions
 

excellent point! Teenagers think everything should be 'fair' and every organization should be a democracy, where everyone gets to vote.

Design-by-committee always results in a system that attempts to do everything, is too big, takes too long, is too expensive, and worst of all, it ends up doing nothing very well.

Every engineering design team that I have been on over the last 21 years had a lead engineer or project engineer who had the final authority over the whole project. You earn that position with years of experience and excellent performance.

Implementation details are left to the rest of the project team, or to individuals who are working on specific subsystems.

As I said before, you have to follow a schedule and meet your milestones, because ship-date is a milestone that will not move, and there is no partial credit (you cant ship half a robot).

As each milestone comes, your lead engineer has to make the final call "this is what we are doing, now lets move on to the next part of the design cycle".

Rather than putting things to a vote, there should be a process for evaluating each idea or concept, a way to put numerical ratings on each aspect of a design, and when you add the + and - columns up, the answer is right there. No need to vote. For engineering projects there are reasons why the best answer is the best answer, not feelings, not pride, not ego.

If you cant show the numbers that support a decision then you havent thought things through in a logical manner. (this has been discussed in other threads).

Re: Rookie Questions
 

let's not get in to the "teen" talk please...