I was again reminded how bluntly excluding everything IT is being built. I wanted to use the phrase "put me in CC of that email". But:
- Does an average person know what it means?
- Or even how to do it in their app?
- What if the field in their app has a different name?
Little IT naming protip:
🙅♂️ Do not use relative project version names like "next", "tng", "legacy", "old". It _will_ eventually confuse people as newcomers won't know if "`old` was before `next`, but that was also before `classic`". It _will_ eventually lose meaning as you release `next-next` and `next-next-next`.
👍 Do use absolute project version names. 1, 2, 3, ... At best irrespective to what new-ism marketing department came with. They want project rebrand? Fine, but we're now on Foo-4.3. So the next one will be Bar-5.0.
So if this is called a "backspace", shouldn't this be called "forwardspace"?
I have a "src" folder for my own source code, or code I've contributed to, but do you have a separate folder for source code from other people? I.e. code you've downloaded just because there are no available binary packages? If so, what do you call it?
It's a good day when you get to crack out the whiteboard and starting figuring out a code structure.
@zbecker @[email protected] @[email protected]
If that changes, it's only much later. Right now, for instance, anybody can use the term "fedi-" as a prefix, even if the particulars they're doing is stuff a majority of others regard as incompatible. Maybe that'll be different in ~10y, maybe it won't. Nobody can know.
Either way, oddness in naming now can get locked in & be impossible to roll back later. There's other examples, like "wiki-" — see Wikileaks: decidedly not within the Wikipedia circle.
Markus Tacker
Michal Bryxí
Pedro Piñera
Michal Bryxí 🌱
Karl
Harry W.
Luke Chadwick
Matthias V
n8 Doesn't follow you 🇺🇦