Sometimes your bug is hardware. Sometimes your bug is software. But wait this software works on that hardware, and this and that hardware are the same, so why does that hardware have a bug? Oh man, I know the feeling. Which is actually why I thought this article was going to go in another direction – but it wound up concluding with something even I wasn’t foreshadowing or have experience with. And that makes it a good read – because debugging is all about variables and if you don’t have control over all of them, you will get different results!
Bugs in software are bad, bugs in hardware are even worse, but inconsistent results are what makes it a total nightmare.
Not my first post on crazy voodoo wasting precious time, I previously approached a similar issue here, so you can call this article “voodoo reloaded” without being far from the truth. Because sometimes those devices we spend so many hours to build – using the best of our logic and know how, seem to defy all that is normal and there remains very little we can do to fix the issues.
Have an amazing project to share? Join the SHOW-AND-TELL every Wednesday night at 7:30pm ET on Google+ Hangouts.
Join us every Wednesday night at 8pm ET for Ask an Engineer!
Learn resistor values with Mho’s Resistance or get the best electronics calculator for engineers “Circuit Playground” – Adafruit’s Apps!
Maker Business — Zenefits founder Parker Conrad takes another crack at HR onboarding
Wearables — Do a dry fit
Electronics — Working with sensitive circuits?
Biohacking — After-Sight : Raspberry Pi Wearable Vision Assistance
No comments yet.
Leave a comment
Adafruit has a "be excellent to each other" comment policy. Help us keep the community here positive and helpful. Stick to the topic, be respectful of makers of all ages and skill levels. Be kind, and don't spam - Thank you!