"It's all just 0's and 1's -- all we do is name them, at various levels of abstraction."
-- (someone, I forget who)
Your "SS" example is triggering for me.. I made that mistake once with a spec for a "Core Security Service". I didn't want to call it "CSS" for some reason so I shortened it, unfortunately.
I got feedback on that, early -- but the story gets worse. This service was part of a product suite with a long name that started with P, and in internal docs everyone had taken to abbreviating that long name "P!" -- the Data Aggregation Service, for example, became "P!DAS".
So naturally, my security service should be called "P!SS". In whatever fonts I was using to write my spec and prepare my presentation, this never looked like the word "piss" to me. But when the final slides got poured into the standard powerpoint template, hours before I was scheduled to present it.. it suddenly hit me.
"It's all just 0's and 1's -- all we do is name them, at various levels of abstraction."
-- (someone, I forget who)
Your "SS" example is triggering for me.. I made that mistake once with a spec for a "Core Security Service". I didn't want to call it "CSS" for some reason so I shortened it, unfortunately.
I got feedback on that, early -- but the story gets worse. This service was part of a product suite with a long name that started with P, and in internal docs everyone had taken to abbreviating that long name "P!" -- the Data Aggregation Service, for example, became "P!DAS".
So naturally, my security service should be called "P!SS". In whatever fonts I was using to write my spec and prepare my presentation, this never looked like the word "piss" to me. But when the final slides got poured into the standard powerpoint template, hours before I was scheduled to present it.. it suddenly hit me.
Truly laughing out loud. Sorry!!!
Never would have seen that coming with the fonts myself. Ouch.