Fred said:
The fact that you use the adjective "complex" to describe the task means
you are not fit for the job. The entire purpose of engineering is to
*make* things, and fundamental to *making* anything is devising a
developmental architecture *simple* enough to facilitate a successful
implementation. This will be more or less of a challenge as a function
of the capabilities of the employees. No amount of simplification will
be sufficient in your work environment, the norm is total and consistent
abject failure, and introducing "process" to the equation is just that
much more overhead, an impediment, and yet another contributor to the
inevitable failure of the entire project- take failure to mean
unworkable, years late, ridiculously expensive, and technologically
obsolete.
Fred,
Thanks for responding to my post. So far it looks like it has angered
many and was not my intention. My intention was to "learn" from others
concerning their successes. Let's say a new engineer showed at your
work. I'm sure you are a very knowledgeable and successful engineer.
What advice would you pass on to him/her concerning success? How do you
measure success? If its not a list of items or habits, then what is
your response? Not to be mean, but do you practice what you preach and
go around your workplace and tell others, "your not fit for the job"?
Or, you pass on some words of wisdom? Anyways, thanks for your
suggestions, it is a good topic, Best Practices, and I'm finding a lot
of important views on engineering.
Thanks Fred,
joe