Hi to all,

I've found a very good article to discuss during months. IMHO, its a must
read for novice EEs (just like me). The subject can be debate with much
further with the valuable thoughts and comments of experienced engineers.
Although its a fee-paying article i couldnt find a way to contact author and
ask for permission. So i have started to OCRed the article. Its three pages
long article and the details of article given below that posting.

So here we go:

"Subtitled 'Advice I wish i'd bad when i started, ' this article by a
long-time engineer presents a road map for moving ahead

During a long and unillustrious career, I've accumulated a few "rules" on
what a young, or perhaps more accurately, a starting, EE should and should
not do on the job. A few came naturallv to me, some were picked up by
observing others, but most were learned the hard way. None were taught when
I went to school.

I wish I could say I eventually practiced all of them myself. The list is
not meant to be comprehensive but rather emphasizes certain points that have
not been discussed much, and that might be useful. I assume, though, that
anyone going into an EE career should really start somewhere in design---of
systems, logic, integrated circuits, analog circuitry, of just about
anything. It's important to get the experience of doing the calculations and
then creating something that's going to be reduced to practice.

GENERALLY SPEAKING. First, some general rules:
1. DO relate what you are doing to the overall system or project
objective.Make it your business to understand how your part of a
project fits into the
system being designed, and what mission or objective that system is trying
to accomplish. Putting it another way, try to understand the big picture.

There are two reasons for doing this. It makes your job more interesting and
exciting and it may suggest a simpler, better approach to your part of the
work than the one someone has laid on you. There are hundreds of cases where
someone completed the assigned part of a larger system and, after learning
the overall objective, pointed out a much better way to accomplish the same
objective. If the people around you are too busy, try asking the boss at
lunchtime to tell you "a
little more" about how you fit into the overall program. And almost always
there are pages and pages that have been written on the subject. Ask to see
the technical proposal your company made or the progress reports on the
program.

Thus, DON'T be afraid to challenge the planned way of doing something or to
propose a new way. Of course, you need to be able to do this with
forethought and a little diplomacy. You don't want to risk becoming a
constant irritant."


Have a nice Sunday.

G=F6khan SEVER.







DOs and DON'Ts for young EEs
Fowler, C.A.;
Spectrum, IEEE
Volume 30, Issue 10, Oct. 1993 Page(s): 59-61

Abstract:
A long-time engineer presents a road map for moving ahead in the electrical
engineering profession. He provides a list of do's and don'ts for promoting
career growth and functioning well on the job

http://ieeexplore.ieee.org/search/wrapper.jsp?arnumber=3D237593
-- =

http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist