So, we were debugging a common ground issue today at a in the amazing Helios Makerspace in Montreal.

We got as far as we could ourselves (debugging one common ground problem, and tracking the data signal through one board and on to the second), then we got stuck. We tried a bunch of things, but it was only when the came in, and determine it was two problems: A second common ground problem, combined with the first (Arduino) board having too many outputs and so not outputting a high enough voltage.

The really interesting part (aside from learning again how important common grounds are) was watching the engineers in the room (the people who were building things, perhaps or perhaps not engineers) all run over as soon as the problem was solved and someone asked the question “So, what was the issue?”

Anytime someone is agonizing over a problem for hours, there is bound to be some learning for those around…Thinking about this from a min/maxing perspective, someone spends hours solving the problem, then you spend 2mins learning about the solution, and then you add it to your list of things to try/check when debugging, taking maybe 30s to possibly reduce your own debugging time by hours.