Do you know what's not accessible?
-
@jtruk @jonathanhogg the general form (a11y, i18n, k8s) has been around a while now.
I think i18n came first, probably because it was easier than repeatedly having the "internationalisation vs internationalization" spelling debate...
But I have seen it said that "k8s" was first because no one could remember how to spell (or pronounce) kubernetes?
Either way, I absolutely hate that this has just become how the tech industry abbreviates things.
It feels like it's on the "smug" side of clever
@lpbkdotnet @jtruk Wikipedia believes that i18n was coined in the 70s and is DEC's fault. Since humans read word-at-a-time by shape, I consider them all to be instances of "I am too lazy to type and therefore you will have to work harder to read"
-
@lpbkdotnet @jtruk Wikipedia believes that i18n was coined in the 70s and is DEC's fault. Since humans read word-at-a-time by shape, I consider them all to be instances of "I am too lazy to type and therefore you will have to work harder to read"
@jonathanhogg @lpbkdotnet None of this excludes 'a11y' being a joke that got out of hand. I think that's a pretty strong candidate here!
-
@jonathanhogg yes! I keep reading it as “ally”
@CatherineFlick @jonathanhogg me too! I’m glad I’m not the only one
-
Do you know what's not accessible? Writing "a11y" in any article or documentation
I will accept it as a convenience in APIs since developers are lazy and can't spell, but fuck off with using it in text
@jonathanhogg I also had to look this up (apart from k8s since my brother works on calico, and it actually sounds vaguely like the actual word). So yeah, and as a system architect - no developers should not be using this shorthand in API's - developers should learn to f&^king spell and express themselves clearly in code/docs/etc or have their work QA'd by people who can
-
Do you know what's not accessible? Writing "a11y" in any article or documentation
I will accept it as a convenience in APIs since developers are lazy and can't spell, but fuck off with using it in text
A8y! I c8y a3e!
-
@lpbkdotnet @jtruk Wikipedia believes that i18n was coined in the 70s and is DEC's fault. Since humans read word-at-a-time by shape, I consider them all to be instances of "I am too lazy to type and therefore you will have to work harder to read"
@jonathanhogg @lpbkdotnet @jtruk But it helps sometimes: try to go a interoperability meeting and you'll see why saying "i14y" is much more pratical.
Whatever the case, in my texts I always put an abbreviation with the expanded term right in the beginning. If it's seldom used, I only write the expanded form.
-
@CatherineFlick @jonathanhogg me too! I’m glad I’m not the only one
@themediumkahuna Oh, does it not? Even knowing it references accessibility, I still assumed it was to be read as "ally."
I hereby declare its use even dumber than I thought.
@CatherineFlick @jonathanhogg -
Do you know what's not accessible? Writing "a11y" in any article or documentation
I will accept it as a convenience in APIs since developers are lazy and can't spell, but fuck off with using it in text
"But it looks like ally, it's great"
Fuck you Jean-Eude. People should not do gatekeeping for something that important.
-
@themediumkahuna Oh, does it not? Even knowing it references accessibility, I still assumed it was to be read as "ally."
I hereby declare its use even dumber than I thought.
@CatherineFlick @jonathanhogg@themediumkahuna
'xsablt' would even make more sense...
@CatherineFlick @jonathanhogg -
Do you know what's not accessible? Writing "a11y" in any article or documentation
I will accept it as a convenience in APIs since developers are lazy and can't spell, but fuck off with using it in text
@jonathanhogg someone wrote a brilliant post about that:
-
R ActivityRelay shared this topic
