3 ms·
The better question is why is 0 next to O. How many programming bugs have resulted in 0 and O being so close together on the keyboard.
by petermcneeley 6y ago
The better question is why is 0 next to O. How many programming bugs have resulted in 0 and O being so close together on the keyboard.
- yakubin 6y agoProbably 0. :) How often do you see a variable named "O"?
- JadeNB 6y agoIt is a real optimist who thinks that the obviously wrong thing to do in code has never been done, or even that it's not the most commonly done thing.
- techbio 6y ago"To tell them apart", a former coworker used the variables named: style1 stylei stylel Ironically, they were still there for some time after I'd left.
- MaxBarraclough 6y agoI'm reminded of the brilliant How To Write Unmaintainable Code. https://github.com/Droogans/unmaintainable-code https://github.com/Droogans/unmaintainable-code
- rvieira 6y agoI think you meant "probably O"
- simonblack 6y agoMany times I notice that I have written a hex number as 'ox1234' instead of '0x1234'. I wonder if that is a subconscious thing as I tend to call '0' as 'oh' rather than 'zero'. (I grew up calling the '0' in phone numbers as 'oh', along with the rest of my cultural peers.)
- hulitu 6y ago> Many times I notice that I have written a hex number as 'ox1234' instead of '0x1234'. On old fonts 0 was ∅ (well not this letter but with a line like in this example) so it was easy to spot it. But we are living on a planet that's revolving and evolving ...
- GekkePrutser 6y agoUgh yeah as an IT person that kind of mistake always bugs me. At my last job someone had labelled all the lockers with "0rder management". It bugged me so much every time I looked at it. For me this is immediately obvious. I don't think the closeness of the two keys have much to do with this error though.
- tinus_hn 6y agoThe original design didn’t have a 1, the l was enough for both. Perhaps the 0 was added as an afterthought as well, after all you could just use the O.