Comment by opello
Or even more likely in a lab setting: have another student test your part in their setup for A/B validation testing.
Or even more likely in a lab setting: have another student test your part in their setup for A/B validation testing.
> 1. Understand the system: Read the manual, read everything in depth, know the fundamentals, know the road map, understand your tools, and look up the details.
Maybe? Although it seems more like it's actually #5:
> 5. Change one thing at a time: Isolate the key factor, grab the brass bar with both hands (understand what's wrong before fixing), change one test at a time, compare it with a good one, and determine what you changed since the last time it worked.
where in my imagined scenario, a student that just finished the lab successfully could pull out their DIP-8 device and swap in the author's to validate that it was possible to make it work in a known good environment.
Sort of like the first debugging tip here:
https://news.ycombinator.com/item?id=42682602