We’ve all been there. After a long day of working in the shop/lab/makerspace/garage, we have made amazing progress on our project, but now as open source hardware developers we have to go back and document what we did. Fellow developers are waiting on the documentation to continue their own work. Fans are waiting so they can follow along at home. And, the very definition of open source hardware means we aren’t really done until we have written sufficient documentation so that someone else can recreate our work.
What a chore! What a pain!
Mach 30’s documentation ground rules help ease this pain by building documentation into the process. Lessons from projects like the Shepard Test Stand and Ground ...