Dumb tech terminology question: is CAGR a commonly-used term when talking about information growth and storage? Or is it a case of the doc author thinking they're being clever but not spelling out acronyms?
'Touched'
Buffistechnology 3: "Press Some Buttons, See What Happens."
Got a question about technology? Ask it here. Discussion of hardware, software, TiVos, multi-region DVDs, Windows, Macs, LINUX, hand-helds, iPods, anything tech related. Better than any helpdesk!
I don't think of it as "tech"? We used it all the time in marketing to financial services industry at Oracle, and in that setting a definition wasn't provided.
This is very much in a context of information wrangling, storage, and scalability, and nothing to do with the financial industry. Which is why I went "Buh?" and googled the term.
Yeah, they totally need to spell that one out for the reader.
It's not a term I know, if that counts for anything.
Or is it a case of the doc author thinking they're being clever but not spelling out acronyms?
Don't they always?
THIS IS WHY THEY NEED TO HIRE ME. Plus I just won buzzword bingo after reading two sentences in this document.
In Journalism school, they taught us to always spell out the first usage of any acronym. I wish that were the case for things that are to be read by people with a wide variety of experience.
In Journalism school, they taught us to always spell out the first usage of any acronym.
We always do that. In large part it's because we have un-American readers, and acronyms/abbreviations aren't the same in other languages (e.g., "AIDS" is "SIDA" in Spanish, and "HIV" is "VIH").
Also many acronyms are acronyms for more than one term. In my recent book the same acronym stood for a technical terms I was using and a union I was writing about. Since neither term was used much, I skipped acronyms for both. Otherwise I would have use the acronyym for the term I used most.
In Journalism school, they taught us to always spell out the first usage of any acronym.
That's what is SUPPOSED to be done in the tech industry. But I have found that many people creating documentation like to throw around acronyms and assume that everyone knows what they stand for. Like a team I worked with that was genuinely surprised to find out that most users didn't automatically parse "Commerce Server Staging" when they read "CSS".