This is a great article. I remember reading this a few years ago during my undergrad- my big takeaway from it was that sometimes you will encounter bugs which you can't solve alone. I always assumed any error I came across was my fault, but that's not good (it's also not good to just assume it's someone else's). Fixing problems in an organization is often a team effort that requires good communication and incentive for improvement- not just one genius coder that knows the whole source code.
I've got a PhD in physics and I have no idea what he's talking about here. Seems like the mainboard layout had issues at higher frequencies which is easily a 100% classical electromagnetism problem. Inductance, impedance and what have you. As another commenter alluded, its only 'quantum' in the sense that all semiconductor behavior is.
I think this is another case where 'quantum' is confused with 'apparently spooky.'
7 comments
[ 4.1 ms ] story [ 20.8 ms ] threadNearly half a dozen? So five? In four years.
It's still interesting, and I don't suppose many people are searching for it so what's the issue with it being posted again?
https://www.pagerduty.com/blog/the-discovery-of-apache-zooke...
The following line tickles my fancy...
> This is the only time in my entire programming life that I've debugged a problem caused by quantum mechanics.
I think this is another case where 'quantum' is confused with 'apparently spooky.'
> bits to get dropped... and the data lost... and the card corrupted.
So as to say that's the Schrodinger's bug that causes several issues at the same time.