Short Acronym Quotes

Spam is not, as some people believe, an acronym for Short, Pointless, and Annoying Messages.

As a rule, any loan that had been turned into an acronym or abbreviation could more clearly be called a “subprime loan,” but the bond market didn’t want to be clear.

One common abbreviation used in Roman letters was SPD, which was short for salutem plurimam dicit, or “sends many greetings.” This served as a greeting at the beginning of a letter, to indicate the sender and the receiver, as in “Marcus Sexto SPD” (“Marcus sends many greetings to Sextus”). Another popular acronym was SVBEEV, which was short for si vales, bene est, ego valeo (“if you are well, that is good, I am well”). Such abbreviations saved space and time, just as acronyms (BTW, AFAIK, IANAL) do today in Internet posts and text messages.

That's a daft name, so you're aware," Loki said. "SHARP Society. It doesn't mean anything and the S is redundant." "It stands for the Society for Hospitable Activities—" Mrs S began, but Loki interrupted. "Yes, I heard you the first time." "We picked an acronym and worked backwards," Theo muttered. "Perhaps you could find something more accurate. You could call yourselves the Society where Hospitality is Ignored Totally. Or, for short—" "Regardless of those trivialities, "we at the SHARP Society are dedicated to observing and intervening as necessary when beings from other realms travel to our planet.

Focus intently and beat procrastination.    Use the Pomodoro Technique (remove distractions, focus for 25 minutes, take a break).    Avoid multitasking unless you find yourself needing occasional fresh perspectives.    Create a ready-to-resume plan when an unavoidable interruption comes up.    Set up a distraction-free environment.    Take frequent short breaks. Overcome being stuck.    When stuck, switch your focus away from the problem at hand, or take a break to surface the diffuse mode.    After some time completely away from the problem, return to where you got stuck.    Use the Hard Start Technique for homework or tests.    When starting a report or essay, do not constantly stop to edit what is flowing out. Separate time spent writing from time spent editing. Learn deeply.    Study actively: practice active recall (“retrieval practice”) and elaborating.    Interleave and space out your learning to help build your intuition and speed.    Don’t just focus on the easy stuff; challenge yourself.    Get enough sleep and stay physically active. Maximize working memory.    Break learning material into small chunks and swap fancy terms for easier ones.    Use “to-do” lists to clear your working memory.    Take good notes and review them the same day you took them. Memorize more efficiently.    Use memory tricks to speed up memorization: acronyms, images, and the Memory Palace.    Use metaphors to quickly grasp new concepts. Gain intuition and think quickly.    Internalize (don’t just unthinkingly memorize) procedures for solving key scientific or mathematical problems.    Make up appropriate gestures to help you remember and understand new language vocabulary. Exert self-discipline even when you don’t have any.    Find ways to overcome challenges without having to rely on self-discipline.    Remove temptations, distractions, and obstacles from your surroundings.    Improve your habits.    Plan your goals and identify obstacles and the ideal way to respond to them ahead of time. Motivate yourself.    Remind yourself of all the benefits of completing tasks.    Reward yourself for completing difficult tasks.    Make sure that a task’s level of difficulty matches your skill set.    Set goals—long-term goals, milestone goals, and process goals. Read effectively.    Preview the text before reading it in detail.    Read actively: think about the text, practice active recall, and annotate. Win big on tests.    Learn as much as possible about the test itself and make a preparation plan.    Practice with previous test questions—from old tests, if possible.    During tests: read instructions carefully, keep track of time, and review answers.    Use the Hard Start Technique. Be a pro learner.    Be a metacognitive learner: understand the task, set goals and plan, learn, and monitor and adjust.    Learn from the past: evaluate what went well and where you can improve.

His breathing even deeper. “So I just … let it be? I just sit there and … feel it?” “Basically, yeah.” “But it feels so awful.” “That’s only because you’re afraid of it. You know what fear stands for?” He blinks. “I didn’t know it was an acronym.” “Well, it is. It’s short for ‘Feeling Excited And Ready.’ You remember that the next time fear comes around. It’s your challenge. And you’re ready for it. Okay?

Speaking on Stage Speakers and presenters have only a few short seconds before their audience members begin forming opinions. True professionals know that beginning with impact determines audience engagement, the energy in the room, positive feedback, the quality of the experience, and whether or not their performance will be a success. A few of the popular methods which you can use to break the ice from the stage are: • Using music. • Using quotes. • Telling a joke. • Citing statistics. • Showing a video. • Asking questions. • Stating a problem. • Sharing acronyms. • Sharing a personal story. • Laying down a challenge. • Using analogies and comparisons. • Taking surveys; raise your hand if . . . Once you refine, define, and discover great conversation starters, you will enjoy renewed confidence for communicating well with new people.

In 2014 the FBI drew ridicule for having compiled a list of 2,800 acronyms and abbreviations used in text messages, Facebook, and, yes, Myspace. It was an Urban Dictionary for the oblivious, paid for with tax money. The list contained a handful of abbreviations that are actually used and known to almost everyone (except some FBI agents). They were accompanied by thousands of obscure or obsolete abbreviations that the feds somehow dredged up. BTDTGTTSAWIO, we’re told, means “been there, done that, got the T-shirt, and wore it out.” The FBI effort demonstrated two points. One is that the life of online abbreviations and slang is short. The other is that those who use abbreviations like BTDTGTTSAWIO don’t care whether anyone understands them. Maybe they’re hoping someone will ask.

It doesn’t take much searching on the Web to find articles giving examples of “improving” your code by using a Setup (now @Before in JUnit). ObjectMother lives under many names, and each name comes with several articles explaining how it’s either successful or the programmer didn’t understand how to correctly apply the pattern. Our tests follow the common advice that above all, code must be DRY. DRY is an acronym for Don’t Repeat Yourself, and is defined as: Every piece of knowledge must have a single, unambiguous, authoritative representation within a system. Both of those pieces of advice are contextually valuable. I can easily think of situations where applying each of those patterns would be the right choice. However, in the context of “I would like to quickly understand this test I’ve never seen before”, those patterns come up short. While working on code written by a teammate or supporting an inherited system, I find myself in the latter context far more often than not.

Is RECON another acronym?” asked Mudflap. (RECON is not an acronym. It’s short for reconnaissance, because reconnaissance is a tough word to spell correctly.) “Um,” said Josh. “Yes. Yes, RECON is an acronym. Now—” “What does it stand for?” asked Splinters. Josh sighed. “Well . . . it . . . stands for . . .” Josh stared at the ceiling of his barracks. He felt instinctively that this was an important test of his leadership. Josh firmly believed that good leaders never admit when they don’t know something. And the fact was, Josh didn’t know what this acronym stood for. (Again, it wasn’t an acronym.) He began to blush a pale plum color. This was a tough spot. What could he do? “RECON stands for . . . Really . . .” He was off to a good start! “Enormous . . . Counterstrike . . .” O. O. O. “On . . .” Aha! Josh was almost there. He screwed up his eyes and willed all his blood to his brain. Josh’s face darkened and became the shade of a turnip. Just one letter left! His eyes lit up. The word came to him like a gift from his ancestors, inscribed in his mind with the ballpoint pen of principals past. “NIMBUSES!

AFGHAN WAR LOGS (EXTRACTS) These logs consist of a short report on every incident regarded as noteworthy by American troops in Afghanistan between January 2004 and December 2009. Around 90,000 incidents are reported in the document passed to WikiLeaks, though only around 75,000 were released. These seven entries detail incidents of civilian casualties caused by British troops in October, November and December 2008. Like other similar reports throughout the logs, they give an insight into the chaotic nature of the battlefield and the constant risk – and consequences of – mistakes by coalition troops. Some of the information in each report has been removed and some acronyms have been expanded for the sake of readability, but each original report can be identified by its number and read in full on the WikiLeaks website. Some of the logs were redacted by WikiLeaks on release.