pcb

Full PCB redline shows an automatically removed test point.

Reviewing component changes and chip shortages

Over the last 6 months, the global semiconductor shortage has been consistently making news for the wave of resulting disruption across the hardware world. From automotive to consumer electronics, virtually every hardware industry has had to scramble to find component replacements ranging from sophisticated ICs to simple microcontrollers.

Reviewing component changes and chip shortages Read More »

Which Git clients work for hardware engineers (and how)

We live at the dawn of a golden age of hardware development. The tools being built are powerful, fast, and focused on saving money and time but not necessarily with an intuitive user interface. Git has a reputation for being clunky and severe, but everyone participating in the tool-building ecosystem has taken Git a long way from its command line only roots.

Which Git clients work for hardware engineers (and how) Read More »

AllSpice new design review creation process.

Design review basics in Git for hardware

Every hardware engineer is familiar with traditional design review. In the past, it made sense to gather a group of people in a room, staring at a projector screen, and manually walk through the schematics and PCB layout. Every person has a chance to voice their input and create action items.

Design review basics in Git for hardware Read More »

Good versus bad commit messages.

Git for hardware: best practices for commits

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.

Git for hardware: best practices for commits Read More »

Scroll to Top