More Best Practices for Engineers

[Genome]

Ooooooo....

Not that we are interested but this showed up in
misc.business.product-dev....

Copied from Google... The original post is not on my news server.

From:[email protected]
Date:Fri, Jun 2 2006 2:06 pm

Hello, I recently posted a list of Best Practices for Hardware
Engineers on another newsgroup. My intention was to learn what are the
key elements or habits that successful engineers do. I am a new
engineer and I do not claim to be an expert on anything. I only have a
desire to learn from the best. Here is my list:

1. Always have a top block diagram, in your schematics and in your FPGA
code
2. Follow the System Engineering Design Process Model
3. Document, Document, Document your work
4. Modularize your work
5. Try a Top Down design approach instead of Bottom Up
6. Ask for Peer Reviews and code walk throughs
7. If a standard exits then follow it.
8. Manage time, don't let time manage you.

Furthermore, in my post I asked people to add anything they wish to the
list, so I wasn't limiting it to 8 items. I received many responses to
my post and I felt from many of the respond ring where irritated at the
very mention of Best Practices. That surprised me and I cannot
understand why. I had a similar experience with the topic of System
Engineering Practices in the workplace. Many responders were just
angered by the topic. Can anyone comment on why people would get
annoyed?

Thanks,
joe

Obviously Guy(??) has explained things.

So, do we need a 'Best Practices for Management'?

1) Don't shit on your employees behind their backs.

Ho Hum

DNA

 

[John Larkin]

Ooooooo....

Not that we are interested but this showed up in
misc.business.product-dev....

Yeah, the BP guy is over there whining as how we weren't nice to him,
inviting GM to pontificate.

And hey, how did your posts sneak in past The Moderator?
Consternation, there was.

Copied from Google... The original post is not on my news server.

9) Go easy on the beer at lunch.

10) Let the wire cool off before you clip the scope probe back on it.

11) Don't breadboard. Don't simulate. They just waste time and dilute
the excitement.

12) When you're really, really behind schedule, take a break.

13) Avoid machining.

14) Source terminate.

15) Orthogonality is your pal.

16) Ground everything, as many places as possible.

17) You're using too many bypass caps, and you don't have enough test
points.

18) Never implement your first idea.

19) Packaging.


John

 

[Genome]

Ooooooo....

Not that we are interested but this showed up in
misc.business.product-dev....

Yeah, the BP guy is over there whining as how we weren't nice to him,
inviting GM to pontificate.

And hey, how did your posts sneak in past The Moderator?
Consternation, there was.

[snip]

John

If the moderator wants the post to get through then he will let it through.

Either you are doing a good impression of someone who will have a sore head
tomorrow or you need to snuggle up to your bed sheets.

DNA

 

[RST Engineering \(jw\)]

1. Always have a top block diagram, in your schematics and in your FPGA

9) Go easy on the beer at lunch.

10) Let the wire cool off before you clip the scope probe back on it.

11) Don't breadboard. Don't simulate. They just waste time and dilute
the excitement.

12) When you're really, really behind schedule, take a break.

13) Avoid machining.

14) Source terminate.

15) Orthogonality is your pal.

16) Ground everything, as many places as possible.

17) You're using too many bypass caps, and you don't have enough test
points.

18) Never implement your first idea.

19) Packaging.

20) There are at least ten different types of capacitors. Learn the
differences.

21) Emitter followers just can't oscillate, but they do.

22) If you can't get the part from at least three independent sources,
consider carefully if you can't do it another way.

23) Annual vacation is meant to restore your mind -- annually, not saved up
for twenty years. Go where noone can find you. Do not use vacation to
paint the house.

24) Dilbert is a documentary (stolen, but I can't remember where).

25) Engineering is an early morning pop quiz and late afternoon lab every
day for the rest of your life.

Jim

 

[Luhan]

20) There are at least ten different types of capacitors. Learn the
differences.

21) Emitter followers just can't oscillate, but they do.

22) If you can't get the part from at least three independent sources,
consider carefully if you can't do it another way.

23) Annual vacation is meant to restore your mind -- annually, not saved up
for twenty years. Go where noone can find you. Do not use vacation to
paint the house.

24) Dilbert is a documentary (stolen, but I can't remember where).

25) Engineering is an early morning pop quiz and late afternoon lab every
day for the rest of your life.

26) Oscillators don't, everything else does.

Luhan

 

[Keith]

26) Oscillators don't, everything else does.

26b) Constants aren't, variables won't.

 

[Rich Grise]

How many of these are actually jokes? ;-)

26) Oscillators don't, everything else does.

And for S/W hackers:

27) Constants aren't, Variables won't. ;-)

Cheers!
Rich

 

[John Larkin]

How many of these are actually jokes? ;-)

# 9.

John