3 ms·
> When I know it's "January" for whatever reason, and not "First Month", without knowing HOW and WHY this is the convention, it sucks. But then you see what Jan
by codeflo 4y ago
> When I know it's "January" for whatever reason, and not "First Month", without knowing HOW and WHY this is the convention, it sucks. But then you see what Janus looks like - which, in this case, makes it even better for some reason than "First Month."
That's interesting, especially because I can't really relate to that. Don't get me wrong, I love this kind of trivia, but not knowing something like that has never been a problem for me at all.
- iainmerrick 4y agoI had the same thought! Is this perhaps related to learning a language as a child versus as an adult? As a child in an English-speaking household, "January" is just one of a million other things to pick up, and you just pick it up. As an adult learner, I can imagine it's very difficult because it seems so random; it's yet another thing that doesn't fit into a system so you have to memorise it and try to internalize it. As a native English speaker, I find it very difficult to remember weekday names and month names in other languages. Mnemonics help, and knowing the derivation of the word can make for a good mnemonic. Edit: re-reading the GP comment, sounds like it's not so much about mnemonics, more that knowing the historical reasons for weird design decisions can make it easier to accept them. Like knowing why "October" isn't actually the eighth month.
- rockzom 4y agoI think it's easier for me to accept weird natural language things from the distant past. But for relatively recent programming language things? Oh man. std::cout << "why"; std::cout << "why"; std::cout << "why";
- bqmjjx0kac 4y agostd::cout << std::endl; // It just rolls off the tongue.
- codeflo 4y agousing namespace std; It's fine, I won't tell anyone.