In my experience, designers and engineers our two very different type jobs. In a R&D group of lets say twenty, there will only be one or two designers, maybe three. The rest are just engineers. The designers think up and write the design specification and the engineers will simply engineer to that specification. The fastest way to kill a company is to burden those one or two designers with paper work. In fact, they might simply just leave. In my opinion, documentation should be the responsibility of the engineers and not the designers.
Thomas
Hello, I'm looking for some information that describes some of the best
> practices or habits for successful electronic design or embedded
> design. I'm trying to convince some co-workers that it is important to
> document their work and follow standards in their designs. Some of my
> co-workers are very fast designers and are respected by their peers,
> but in their rush to get the design done they often ignore standards
> and don't document their work, such as in their schematics or in their
> FPGA code. I feel these habits and behavior actually wastes money, by
> that I mean that if someone has to take their undocumented work, they
> won't know what is going on. I realize that I might not be able to
> change more senior engineers, but I might be able to leave an
> impression on the newer engineers. If anyone knows of some habits or a
> list of some best practices that make a successful design, please pass
> them onto me. Most of these habits I would assume fall into proper
> system engineering.
>
> thanks,
> joe
>