Documenting Breadboaring and Mods

CheapSuitG

CheapSuitG

The TubeSchemer
Hello there!

I’m notoriously unorganized when left to my own devices, it gets bad fast.

That said I actually do really well when there’s a structure in place. My parts inventory system is pretty dialed in with formulas tracking stock levels, auto generated shopping lists, backlog builds and pages of vendor links and references.

Lately I’ve been getting deep into breadboarding and experimenting with circuit ideas and I want to make sure I have a solid way to document everything. Otherwise, I’ll forget what I just built within five minutes.

I’ve wanting put together something that I can print out and scribble on while I’m working and then enter it for later reference. Does anyone have something like this I can use as a jumping off point? I have a couple thoughts but it is usually more fun when you steal an idea.

Thanks!
 
I hand draw schematics on a full size sheet of paper with the circuit name, where I obtained the schematic from, any relevant notes I've come across, the date I breadboarded it, and then any notes or changes. Then it goes in a file folder
 
I have been using printed copies of schematics, marking them up.

I guess more so I am looking for ways to document the changes and the why. Still learning and while I understand the changing a value does, I have to hear it to fully get it. Also, learning what pairings I like and what I don't. One thing I never though about when I started this was "feel".

Here is a super quick mock up of what I typically end up with but has 100 times more notes and in a 3rd graders handwriting.



1778624431229.png
 
You must log in or register to reply here.
Back
Top