Git has become an essential tool in modern software development workflows, providing a robust and flexible foundation for version control and collaboration. But, it’s not limited to just code. It is also used for versioning and tracking changes in various types of files and projects, including hardware development.
Our co-founder Kyle Dumont joined Chris Gammell in episode #505 of The Amp Hour Electronics Podcast to talk about revision control for hardware projects.
We sat down to talk to Macrofab Engineering Podcast hosts Parker Dillmann and Stephen Kraig. Macrofab is a PCB and Electronics Manufacturing platform.
Need to organize schematic, PCB and supporting files? Here are some ways to do so more easily by setting up your Altium project on Git.
Hardware engineers are all too familiar with what in-person design reviews look like. As engineering evolves, however, they are being replaced by asynchronous collaboration on a platform. Here’s why many in-person meetings are being replaced by digital design reviews.
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 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.
We’ve been asked the question, “How can I best manage large complex projects with multiple PCBAs?” Here’s an overview.
Revision control is a continuous process, with every change and edit tracked, allowing you to pick and choose each of these edits to create a new change. Meanwhile, releases give the ability to point to a specific moment in the change history without ambiguity.