I've done a ton of low-budget analog hardware debugging, and the major problem with hardware debugging is each attempt to fix the problem takes a long time. If I had wanted to test every idea I had I could easily waste a week. Not to mention that I can't just run some automated test suite after the fact. For hardware, approaching debugging methodically is a necessity, not just best practice.

We don't typically have log files for hardware, but I'm always surprised when otherwise extremely intelligent people first try to debug by applying "fixes" that shouldn't have any causal effect on any weird observations we've gotten. I have no problem with people coming up with theories because each modification takes time, but each theory should ideally explain the data...

Reading log files with really obscure error messages might as well be reading a magical grimoire. Especially when the solution turned out to have nothing to do with the error message.

Hey but that is not a discussion, that's just throwing anecdote to bring other person down or make yourself feel better.

The funny thing is this comment could have just as well been made on the grandparent and would read just as well.