Mixing up my p's and q's, and my b's and d's were a big problem when I was young but I luckily grew out of that since they were considering putting me into remedial education because of it.
I also find I've developed a lot of my own pneumonics. So for > and < I know that the converging side is narrow and therefore it is the lesser side, the divering side is broad and as such is the greater side. Or as someone from the west coast of an island - I figure out east and west by imaging my country knowing that I'm on the west coast.
Funnily enough north/south or up/down don't cause me trouble. It's only things that have vertical symmetry or that can rotate that confuse me.
Almost 10 years in the states and I still have to think before every single git commit.
Source: I'm Portuguese.
I mean, I thought it was just like the article, but if it's also confounding directions (sometimes I have to think about left and right, I sometimes think that California is on the east coast, I make a mess with clockwise/counterclockwise) then I have that problem too.
mnemonics :P
I mean, I never really thought about it, but that's how I "know" which is slash forward and which is backslash.
[0] https://static.fjcdn.com/pictures/Slash_066306_2216065.jpg
/ forward slash
\ backward slash
- Do you have problems disambiguating P and d?
- Do you have problems disambiguating d and b?
If I have an external visual queue I can use, I'm good to go. That's what made the >< thing work. I got the intersection/union symbols down because union happens to both look like and start with a U.
I don't understand this at all. The bigger number is at the bigger end, that's the whole point of the symbols. What does the alligator introduce, apart from an extra step and doubt over whether it's larger or smaller numbers they are said to eat?
It probably has to do with how it was taught. I was never taught "the bigger number is at the bigger end", it was simply "> means greater than and < means less than" and we were supposed to memorize that. The alligator mneumonic is just a way of recovering the original meaning.
For me, it's any arbitrary, binary, convention. Left and right. Clockwise and counterclockwise. \ and /. Whether time zone offsets are added or subtracted from the UTC time. Interestingly, < and > never gave me a problem, perhaps because I've internalized the alligator mnemonic you mentioned.
Do you use some special fonts that help with symbols such as > and <, b and d and so on?
For left-handed people, it's a bit more complicated.
Not so complicated.
If you ever stare at a single word it's never muddled or back to front, but when you scan a sentence and think back over what you have seen words may be in different orders, perhaps based on a typical grouping for those words.
For example if you scanned over your comment, it could come out as, "it does mix dynamical while reading". "It does" and your typo being corrected.
Try staring at a group of 5-6 words quickly, close your eyes, visualize them and read them back.
For me it's like there is a limited buffer, so when I parse a sentence and then read it back in context the start may have become corrupted.
I simply can't tell the difference between symbols that have been rotated or reversed. So I made it through an engineering degree with "the alligator eats the bigger number" mnemonics for > and <.
The first thing I do when I get a new dev machine is take a pen and write "\r\n" up above the delete key. I've never gotten the slashes in the right direction on that key sequence from memory even though I type them several times a day (I just had to edit my post after looking it up right now and realizing I'd typed it wrong on my new laptop).
Anything that can be reversed, I reverse roughly 50% of the time. Because to my brain, they're interchangeable.