A simple miscommunication or lost update can cause a domino effect that spreads across huge portions of an organization and its stakeholders within multiple teams. Its impact can throw business goals off the rails; stalling new projects, delaying other customer orders, and frustrating employees. Alignment is far more than a buzzword – taking these steps to keep everyone on the same page is well worth the effort.
In the world of software development, Git has etched its name as the go-to version control system. Git’s advantages to productivity and focus on continuous improvement have helped spawn entire industries. But what about its application in the realm of hardware?
We’ve been asked the question, “How can I best manage large complex projects with multiple PCBAs?” Here’s an overview.
Most electronics designs are more complicated than a single PCBA. Very often, designs are compartmentalized into multiple interconnected PCBAs, wiring harnesses, enclosures, mechanical fasteners, labels, packaging, and anything else necessary to run the design.
One of the biggest differences between using Git for software vs Git for hardware is that software tends to use Git as source control whereas hardware tends to use Git as version control.
Revision control can be overwhelming when first starting out. Engineers used to releasing files once per PCBA revision can be daunted by commits. It’s very easy to finish working on a section of a schematic and instantly jump to another. Keeping the development momentum flowing is important.