Searching \ for '[OT] Top 10 list of engineering fallacies' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/index.htm?key=top+list+engineering
Search entire site for: 'Top 10 list of engineering fallacies'.

Exact match. Not showing close matches.
PICList Thread
'[OT] Top 10 list of engineering fallacies'
2006\09\20@021847 by Gökhan SEVER

picon face
1. Two engineers = twice the output
2. The initial specification is complete and entirely accurate.  Any errors
or omissions found will have no schedule effect.
3. If the start date slips, there is no reason to change the completion
date.
4. There is no schedule impact caused by features and requirements added
after the schedule is agreed to.
5. There is no need for further work as soon as the main features appear to
be operational.
6. Any manager can make a better decision during a meeting, than any
engineer can after three months study.
7. Engineers don't understand business.
8. There is no schedule impact caused by management re-assigning n members
of the team.
9. Experience doesn't matter. Anyone who can create a program that appears
to work is just as good as anyone else. "My son is still in high school and
he can program circles
around you."
10. "If you really cared about this project and this company and your job,
you would work harder."

2006\09\20@024209 by William Chops Westfield

face picon face

On Sep 19, 2006, at 11:18 PM, Gökhan SEVER wrote:

> 9. Experience doesn't matter. Anyone who can create a program
> that appears to work is just as good as anyone else.

This needs modernized...

All they have to do is follow the processes set forth in the
companies ISO9000 process definitions.  The individual's
experience, skillset, or temperament is irrelevant as long
as the process is adequately documented.

 :-)
BillW

2006\09\20@051029 by genome

picon face
part 1 1725 bytes
> 9. Experience doesn't matter. Anyone who can create a program
> that appears to work is just as good as anyone else.

Experience will not help you if you dont have the brains to do it...
Seniority shouldn't be a prime factor in science and engineering because its
all about whose got the best and most brilliant idea...

>>All they have to do is follow the processes set forth in the
>>companies ISO9000 process definitions.

I think Galileo or whats his name was, once said "The man who know's the
how's of things will always be successfull but the man who know's the why's
of things will always be his BOSS"...... so engineering is not all about
just following regulations eather.. you have to think.. you have to use your
head... thats what engineers should do... we would not be where we are right
now in terms of technology, the tallest building will not be built... the
fastest aircraft will not be a reality, You wont be there right now with
your computer... if engineers were merely following standards... Engineers
today try to beat the odds.. inventing new ideas that years ago were beyond
comprehension...

"William Chops Westfield" <spam_OUTwestfwTakeThisOuTspammac.com> wrote in message
news:.....d9a4ffc56a54ba5ee47356418cc0b931KILLspamspam@spam@mac.com...

On Sep 19, 2006, at 11:18 PM, Gökhan SEVER wrote:

> 9. Experience doesn't matter. Anyone who can create a program
> that appears to work is just as good as anyone else.

This needs modernized...

All they have to do is follow the processes set forth in the
companies ISO9000 process definitions.  The individual's
experience, skillset, or temperament is irrelevant as long
as the process is adequately documented.

 :-)
BillW

More... (looser matching)
- Last day of these posts
- In 2006 , 2007 only
- Today
- New search...