My Hardest Bug Ever (2013)
gamasutra.com
My Hardest Bug Ever (2013)
1–8 of 8 posts
Re: My Hardest Bug Ever (2013)
#2Re: My Hardest Bug Ever (2013)
#3Re: My Hardest Bug Ever (2013)
#4https://www.pagerduty.com/blog/the-discovery-of-apache-zooke...
Re: My Hardest Bug Ever (2013)
#5This is from 2013, and has been posted nearly a half dozen times now: https://hn.algolia.com/?query=http:%2F%2Fwww.gamasutra.com%2...
Nearly 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?
Re: My Hardest Bug Ever (2013)
#6The 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.
Re: My Hardest Bug Ever (2013)
#7Anyone a bit more savvy on hardware able to shed a bit more light on this? 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.'
Re: My Hardest Bug Ever (2013)
#8Anyone a bit more savvy on hardware able to shed a bit more light on this? 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'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.'
> 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.