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: snipped-for-privacy@hotmail.com
>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