EDN has published a community-style roundup of practical advice for electrical engineers, focusing on habits that improve everyday work rather than on a single technical topic. The post frames the suggestions as lessons learned over years in engineering roles and invites additional input from readers.
Among the concrete points is a strong emphasis on documentation. The author argues that keeping clear records helps not only current teammates but also the original engineer when a project resurfaces later and details are no longer fresh.
Another recurring theme is cross-functional input during design. The piece recommends bringing repair personnel into design discussions so that maintainability is considered early, especially if the next product revision is expected to benefit from easier serviceability. In the same spirit, the author suggests involving a machinist before a design is finalized, since that perspective can reveal ways to simplify mechanical fabrication.
The article also notes that electrical engineers often end up doing mechanical design work as part of hardware development. Rather than treating that as a separate discipline, the advice presented here is to use nearby expertise early and to look for practical simplifications before committing to the final design. The result is a short, experience-based checklist of working principles for embedded hardware, firmware, and system design.