I imagine people couldn't decide on which conjunction to use since they both work, used both incorrectly, stopped using plain "else", then started thinking they needed to prefix "or" before "else". Dictionaries then adjusted, removing the conjunction entry of "else" and adding "or else" as a conjunctive phrase.
You can also say "elsewise", which to me still sounds a little old school, but more natural than just using "else" like we do in programming languages.
It's almost tempting to reach for "elsewhen" or "elsewhy", since we have "elsewhere". But if saying "elsewise" feels like chatting with a very elderly relative, saying those ones feels more like a seance with distant ancestors. But apparently it used to be a thing!
I my head as a child I instantly understood and thought "Ahhh, they mean like 'OR else this happens.'
I have always assumed it was a boolean logic thing meant to help show that it wasn't an AND, but 'or' had already been used as a keyword so they did 'or else' and dropped the reserved 'or'.
"Else" is definitely extremely commonly used in English today, just not in the US. The UK says "else" instead of otherwise. "We'll see if the bar is open, else we can go across the street".
It's not uncommon in the US. I'm confused why people think so. It must be regional or cultural variation? Maybe you know it if you're over 35, else not?
A novice asked the master: “What must I do to learn the Zen of Backup?” The master whacked the novice in the head, grabbed the keyboard, and ran sudo rm -rf /. The novice smiled and left feeling enlightened.
Forgive me for my ignorance: Why should the Rodin Museum be obligated to provide 3D scans of Rodin’s sculptures? OP jumps into legal arguments about FOI without connecting the dots from the law to the point clouds.
This isn’t really a paradox if you just visualize the Moon as a sphere and visualize where the Sun is shining from, and I think that’s what the plots in OP demonstrate.
The “paradox” might be in the initial assertion which does not use an accurate mental model: “After sunset, the sun is below, so we would expect the illuminated portion of the moon to point down, towards where the sun is.” This assertion might be true if at sunset the Sun ducks just behind the horizon, around the same distance or closer than the Moon is to the Earth. In reality, the Sun is of course much farther from Earth than the Moon. Factoring the relative distances into the mental model will lead you to the correct conclusion.
src/
md/
README.md # index of all md, entry point for agents
TODO.md # a list of general TODOs open for this module
OVERVIEW.md # a technical overview of this module
features/FEATURE_1.md # a set of feature-specific documents
data/DATAMODEL_1.md # descriptions of data models in the module
api/API_1.md # descriptions of APIs the module provides
infrastructure/INFRASTRUCTURE_1.md # descriptions of infrastructure used by the module
What if we standardized on README.md in each subdirectory alongside the code?
src/
README.md # entry point for humans and agents
TODO.md # list of general TODOs open for this module
INFRA.md # descriptions of infrastructure used by the module
api/
README.md # descriptions of APIs the module provides
models/
README.md # descriptions of data models in this module
README.md in each subdirectory seems to align better with OP’s objective “that Markdown should be checked in to /src, next to the code it produces”. It is also a convention already in use in many code repositories.
MDs in subdirectories is how Anthropic recommends it too. If you have a CLAUDE.md in a subdirectory and an agent starts working in there, it's appended
reply