3 ms·

The part about nonsense words is great (one of my pet peeves) but how do you accomplish that in practice? Everything has to have a name. For example, when you'r

The part about nonsense words is great (one of my pet peeves) but how do you accomplish that in practice? Everything has to have a name. For example, when you're developing Windows 8 what would you call Metro Mode? "Alternate touch optimized desktop UI" is a bit of a mouthful.

whatshisface 9y ago
I'd call it the Touch UI, the others could be Windowed and Mobile.
xarball 9y ago
Metro's branding was a failure of imagination and a failure to properly capture and convey intent. There are many other options out there: | "Touch UI" | "Mobile UI" | "Everywhere UI" | "Fisher-Price UI" | ... or my personal favorite... | "Mega-Bloks" |
simplicio 9y ago
I think pretty much every industry and field quickly develops it's own stock of acronyms, nicknames, jargon etc. This can feel alienating to "outsiders", which is why people don't like it, but I think its pretty necessary (and inevitable). If you're working with a set of concepts, processes, software everyday, developing a shorthand way of talking (and thinking) about them is a big timesaver both in terms of communication and mental effort.
- gregknicholson 9y ago
  > If you're working with a set of concepts, processes, software everyday, developing a shorthand way of talking (and thinking) about them is a big timesaver both in terms of communication and mental effort. For internal processes, this is fair enough. But anything that will be exposed to an end-user should be simple without shorthand.
ScottBurson 9y ago
Maybe just try really hard to maintain a centralized glossary, that people actually use and keep up to date.
manigandham 9y ago
As usual, common sense applies. The issue is regarding unnecessary names. If it's really a product name or industry wide then use it, but many companies tend to come up with acronyms that are only used internally or within a single team and this hurts communication. For your example, just call it touchscreen mode.
notatoad 9y ago
how many new UIs was the windows team developing at the time? shouldn't "the new UI" suffice?
- maltalex 9y ago
  “New” is a bad way to refer to something. It loses meaning once the new thing isn’t so new or has been replaced by something newer. Say a document talks about “the new windows UI” and there were like 5 different versions of “new ui” during the lifetime of the project. Which version is the document talking about?

whatshisface 9y ago

I'd call it the Touch UI, the others could be Windowed and Mobile.

xarball 9y ago

simplicio 9y ago

I think pretty much every industry and field quickly develops it's own stock of acronyms, nicknames, jargon etc. This can feel alienating to "outsiders", which is why people don't like it, but I think its pretty necessary (and inevitable). If you're working with a set of concepts, processes, software everyday, developing a shorthand way of talking (and thinking) about them is a big timesaver both in terms of communication and mental effort.

gregknicholson 9y ago
> If you're working with a set of concepts, processes, software everyday, developing a shorthand way of talking (and thinking) about them is a big timesaver both in terms of communication and mental effort. For internal processes, this is fair enough. But anything that will be exposed to an end-user should be simple without shorthand.

ScottBurson 9y ago

Maybe just try really hard to maintain a centralized glossary, that people actually use and keep up to date.

manigandham 9y ago

As usual, common sense applies. The issue is regarding unnecessary names. If it's really a product name or industry wide then use it, but many companies tend to come up with acronyms that are only used internally or within a single team and this hurts communication. For your example, just call it touchscreen mode.

notatoad 9y ago

how many new UIs was the windows team developing at the time? shouldn't "the new UI" suffice?

maltalex 9y ago
“New” is a bad way to refer to something. It loses meaning once the new thing isn’t so new or has been replaced by something newer. Say a document talks about “the new windows UI” and there were like 5 different versions of “new ui” during the lifetime of the project. Which version is the document talking about?