Should Acronyms Be In Quotes

From time to time, Musk will send out an e-mail to the entire company to enforce a new policy or let them know about something that’s bothering him. One of the more famous e-mails arrived in May 2010 with the subject line: Acronyms Seriously Suck: There is a creeping tendency to use made up acronyms at SpaceX. Excessive use of made up acronyms is a significant impediment to communication and keeping communication good as we grow is incredibly important. Individually, a few acronyms here and there may not seem so bad, but if a thousand people are making these up, over time the result will be a huge glossary that we have to issue to new employees. No one can actually remember all these acronyms and people don’t want to seem dumb in a meeting, so they just sit there in ignorance. This is particularly tough on new employees. That needs to stop immediately or I will take drastic action—I have given enough warnings over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary. If there is an existing acronym that cannot reasonably be justified, it should be eliminated, as I have requested in the past. For example, there should be no “HTS” [horizontal test stand] or “VTS” [vertical test stand] designations for test stands. Those are particularly dumb, as they contain unnecessary words. A “stand” at our test site is obviously a *test* stand. VTS-3 is four syllables compared with “Tripod,” which is two, so the bloody acronym version actually takes longer to say than the name! The key test for an acronym is to ask whether it helps or hurts communication. An acronym that most engineers outside of SpaceX already know, such as GUI, is fine to use. It is also ok to make up a few acronyms/contractions every now and again, assuming I have approved them, eg MVac and M9 instead of Merlin 1C-Vacuum or Merlin 1C-Sea Level, but those need to be kept to a minimum.

The latest literature says we’re supposed to call them “post-Kellis-Amberlee amplification manifestation syndrome humans,” but fuck that. If they really wanted some fancy new term for “zombie” to catch on, they should have made it easy to shout at the top of your lungs, or at least made sure it formed a catchy acronym

They had had half an hour. He walked with her to Whitehall, toward the bus stop. In the precious final minutes he wrote out his address for her, a bleak sequence of acronyms and numbers. “then, at last, he took her hand and squeezed. The gesture had to carry all that had not been said, and she answered it with pressure from her own hand. Her bus came, and she did not let go. They were standing face to face. He kissed her, lightly at first, but they drew closer, and when their tongues touched, a disembodied part of himself was abjectly grateful, for he knew he now had a memory in the bank and would be drawing on it for months to come. He was drawing on it now, in a French barn, They tightened their embrace and went on kissing while people edged past them in the queue. She was crying onto his cheek, and her sorrow stretched her lips against his. Another bus arrived. She pulled away, squeezed his wrist, and got on without a word and didn’t look back. He watched her find her seat, and as the bus began to move realized he should have gone with her, all the way to the hospital. He had thrown away minutes in her company. He must learn again how to think “and act for himself. He began to run along hoping to catch up with her at the next stop. But her bus was far ahead

I offer the acronym EASE to assist our city designers. To enable the passeggiata, our cities should be easy (to walk); accessible (to all); safe (for everyone), and enjoyable (for all).

In my book, though, they should have changed Unidentified Flying Objects to Mysterious Otherworldly Flying Objects—or MOFOs. This name was more accurate after all. And I’d give my last dollar to hear TV reporters using the new acronym.

Looking back on it, could there possible have been a more confusing acronym for trying to keep kids from experimenting with drugs than DARE? "Kids, we’re here today to DARE you not to do drugs! We DARE you to accept our DARE!" "Office, does that mean you want us not to do drugs, or to do drugs?" “We DARE you not to do drugs!” "But I thought we weren’t supposed to do things We’re dared to do. If you dared me to jump out of a tree, I should do that, right?" "It’s just an acronym, son." "What is an acronym?

There will be others, many others. You’ll try desperately to digest a single word through the acronym-laden gibberish, while beginning to wonder what the point of all this is, and also why you didn’t feel that staple you just sent into your thigh. You usually do. You’ll wonder what your company even does. After six years, you have no idea what an information system is, do you? Maybe you should ask. Maybe that’s how this ends. You’ll imagine how poetic it would be to simply unmute yourself and say, “Sorry to interrupt, guys, but what’s an information system?” Still, your mind will drift further, envisioning how much more tolerable this call would be if you could just slowly masturbate during it. So you do. You masturbate during it. And it’s beautiful. Masturbating, invisible within your three-walled fortress. Invisible… invisible… practically invisible.

The five letters of the SOLID acronym stand for: Single Responsibility Principle: a class should have one and only one responsibility; that is, only one reason to change. The Lack of Cohesion Of Methods metric indicates the antipattern of too large a class. Open/Closed Principle: a class should be open for extension, but closed against modification. The Case Statement design smell suggests a violation. Liskov Substitution Principle: a method designed to work on an object of type T should also work on an object of any subtype of T. That is, all of T’s subtypes should preserve T’s “contract.” The refused bequest design smell often indicates a violation. Dependency Injection Principle: if two classes depend on each other but their implementations may change, it would be better for them to both depend on a separate abstract interface which is “injected” between them. Demeter Principle: a method can call other methods in its own class, and methods on the classes of its own instance variables; everything else is taboo. A design smell that indicates a violation is inappropriate intimacy.

Acronyms Seriously Suck: There is a creeping tendency to use made up acronyms at SpaceX. Excessive use of made up acronyms is a significant impediment to communication and keeping communication good as we grow is incredibly important. Individually, a few acronyms here and there may not seem so bad, but if a thousand people are making these up, over time the result will be a huge glossary that we have to issue to new employees. No one can actually remember all these acronyms and people don’t want to seem dumb in a meeting, so they just sit there in ignorance. This is particularly tough on new employees. That needs to stop immediately or I will take drastic action—I have given enough warnings over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary. If there is an existing acronym that cannot reasonably be justified, it should be eliminated, as I have requested in the past. For example, there should be no “HTS” [horizontal test stand] or “VTS” [vertical test stand] designations for test stands. Those are particularly dumb, as they contain unnecessary words. A “stand” at our test site is obviously a *test* stand. VTS-3 is four syllables compared with “Tripod,” which is two, so the bloody acronym version actually takes longer to say than the name! The key test for an acronym is to ask whether it helps or hurts communication. An acronym that most engineers outside of SpaceX already know, such as GUI, is fine to use. It is also ok to make up a few acronyms/contractions every now and again, assuming I have approved them, eg MVac and M9 instead of Merlin 1C-Vacuum or Merlin 1C-Sea Level, but those need to be kept to a minimum. This was classic Musk. The e-mail is rough in its tone and yet not really unwarranted for a guy who just wants things done as efficiently as possible. It obsesses over something that other people might find trivial and yet he has a definite point. It’s comical in that Musk wants all acronym approvals to run directly through him, but that’s entirely in keeping with the hands-on management style that has, mainly, worked well at both SpaceX and Tesla. Employees have since dubbed the acronym policy the ASS Rule.

Established in 1923, the OGPU replaced the Cheka as Russia’s central organ of the secret police. In 1934, the OGPU would be replaced by the NKVD, which in turn would be replaced by the MGB in 1943 and the KGB in 1954. On the surface, this may seem confusing. But the good news is that unlike political parties, artistic movements, or schools of fashion—which go through such sweeping reinventions—the methodologies and intentions of the secret police never change. So you should feel no need to distinguish one acronym from the next.]

FOGLAMP project checklist FOGLAMP is an acronym for focus, oversight, goals, leadership, abilities, means, and process. This tool can help you cut through the haze and plan your critical projects. Complete the table for each early-win project you set up. Project: __________________________ Question Answer Focus: What is the focus for this project? For example, what goal or early win do you want to achieve? Oversight: How will you oversee this project? Who else should participate in oversight to help you get buy-in for implementing results? Goals: What are the goals and the intermediate milestones, and time frames for achieving them? Leadership: Who will lead the project? What training, if any, do they need in order to be successful? Abilities: What mix of skills and representation needs to be included? Who needs to be included because of their skills? Because they represent key constituencies? Means: What additional resources, such as facilitation, does the team need to be successful? Process: Are there change models or structured processes you want the team to use? If so, how will they become familiar with the approach?

Reflection • Think of a desirable but unrealistic outcome. Why exactly it is unrealistic? Whose comfort zones does it disrupt? Idea • Courageous goals have their own momentum. They force a change of scene, raise entirely new questions, and call new relationships into being. Tool • Use the Courageous Goal Starter Kit to get things moving: 1) Dream it, 2) Declare it, and 3) Get started. Tool • Make it sticky with SUCCES: Get more buy-in for your Courageous outcome by describing it using the principles defined by Chip and Dan Heath and their acronym, SUCCES – it should be 1) Simple, 2) Unexpected, 3) Concrete, 4) Credible, 5) Emotional, and 6) contain a Story.

Like the proverbial Pushmi-pullyu of Hugh Lofting’s Doctor Dolittle stories, Westminster feels itself pulled in two directions at once by two different ‘heads’. One minute it worries about losing powers to Brussels. The next minute it worries about losing powers to Edinburgh. One minute it talks about a referendum on whether the UK stays in the EU. The next minute it agrees to a referendum on whether Scotland should stay in the UK. Caught between the two centres of power it sometimes seems to be paralysed. When the Scots claim that they can stay in the EU after leaving the UK, the Prime Minister is the first to warn them that this may not be so. But when they hear his stern lectures to the EU and about a possible ‘Brexit’ (British exit), they may well feel that leaving the UK is actually the only way of ensuring that they stay in the EU. Paradoxically, the more UKIP (the United Kingdom Independence Party) calls for the UK to leave the EU, the more Scots may feel that their safest bet is to leave the UK, leaving UKIP presumably to campaign as the Former United Kingdom Independence Party, a situation which at the very least will give it an unfortunate acronym.

When the retail, operations, and finance teams began to construct the initial Amazon WBR, they turned to a well-known Six Sigma process improvement method called DMAIC, an acronym for Define-Measure-Analyze-Improve-Control.1 Should you decide to implement a Weekly Business Review for your business, we recommend following the DMAIC steps as well. The order of the steps matters. Progressing through this metrics life cycle in this order can prevent a lot of frustration and rework, allowing you to achieve your goals faster.

Fine is an acronym for Freaked out, Insecure, Neurotic, and Exhausted. So, do you want to try again, or should I just drop it?

I endeavor in life never to be anything more than defensively prejudiced-- certainly not haughty-- but this sort of unbridled use of capital letters and acronyms should have been omen enough to keep me home

How to set a goal. Several decades ago, renowned management consultant Peter Drucker popularized a system of goal defining and achievement known as the SMART Criteria, a mnemonic acronym to optimally structure the setting of objectives. It works for me, it will work for you. I’ve supplemented it with my own spin. It goes like this: Specific. A goal must be clear and unambiguous; without vagaries and platitudes. It must indicate exactly what is expected, why is it important, who’s involved, where is it going to happen, and which attributes are important. Measurable. A goal must include concrete criteria for measuring progress toward its attainment. If a goal is not measurable, it is not possible to know whether you’re making progress toward successful completion. Attainable. A goal must fall within realistic parameters, accessible enough to craft a logical roadmap toward its achievement. However, I would provide the personal caveat that no goal worthy of your complete attention, time, and resources should be too realistic. It should be big. Big enough to scare you. Audacious enough to tingle the senses, keep you up at night, and launch you out of bed in the morning. In preparation for my first Ultraman, I never missed a single workout, primarily because I was scared out of my mind. That said, a goal must be rooted in tangible reality. Understand the distinction between audacious and ludicrous. Relevant. This takes us back to the spirituality of pursuit. A goal must contain personal meaning. You should understand why its pursuit holds importance in the context of your personal growth. In other words, it has to matter. The more it matters, the better. Time-bound. A goal must have a target date and be grounded within a specific time frame. Deadlines create structure, foster a sense of urgency, and focus the prioritization of time and energy. Service-oriented. This is my personal addition to the criteria (so now it’s “SMARTS”). Although a goal must carry great personal meaning, in my experience, the pursuit of that goal is best served when it is also in service to something beyond the self. This can take any number of forms: raising money for a cause you believe in; perhaps a blog chronicling the journey to inspire friends and family. It doesn’t matter. What does matter is the spirit in which you approach it.

Another reason why I've been slow to answer is that I've been working on something I've tried to get behind for 12 years: a sequel to MAN IN THE HIGH CASTLE. Maybe I should keep you posted about it; possibly it will be the best thing (so to speak) that I've done or will do. Working title is: VALISYSTEM A. That's an acronym for "Vast Active Living Intelligence System" A. I have a 7-page letter on the subject addressed to Peter Fitting, one of the Marxist writers; if I can get it together to get a Xerox, I'll send it to you. Bear with me, please, because I am lazy & disorganized. But brilliant (you knew that).

There is a creeping tendency to use made up acronyms at SpaceX. Excessive use of made up acronyms is a significant impediment to communication and keeping communication good as we grow is incredibly important. Individually, a few acronyms here and there may not seem so bad, but if a thousand people are making these up, over time the result will be a huge glossary that we have to issue to new employees. No one can actually remember all these acronyms and people don’t want to seem dumb in a meeting, so they just sit there in ignorance. This is particularly tough on new employees. That needs to stop immediately or I will take drastic action—I have given enough warnings over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary. If there is an existing acronym that cannot reasonably be justified, it should be eliminated, as I have requested in the past. For example, there should be no “HTS” [horizontal test stand] or “VTS” [vertical test stand] designations for test stands. Those are particularly dumb, as they contain unnecessary words. A “stand” at our test site is obviously a *test* stand. VTS-3 is four syllables compared with “Tripod,” which is two, so the bloody acronym version actually takes longer to say than the name! The key test for an acronym is to ask whether it helps or hurts communication. An acronym that most engineers outside of SpaceX already know, such as GUI, is fine to use. It is also ok to make up a few acronyms/contractions every now and again, assuming I have approved them, eg MVac and M9 instead of Merlin 1C-Vacuum or Merlin 1C-Sea Level, but those need to be kept to a minimum. This

From time to time, Musk will send out an e-mail to the entire company to enforce a new policy or let them know about something that’s bothering him. One of the more famous e-mails arrived in May 2010 with the subject line: Acronyms Seriously Suck: There is a creeping tendency to use made up acronyms at SpaceX. Excessive use of made up acronyms is a significant impediment to communication and keeping communication good as we grow is incredibly important. Individually, a few acronyms here and there may not seem so bad, but if a thousand people are making these up, over time the result will be a huge glossary that we have to issue to new employees. No one can actually remember all these acronyms and people don’t want to seem dumb in a meeting, so they just sit there in ignorance. This is particularly tough on new employees. That needs to stop immediately or I will take drastic action—I have given enough warnings over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary. If there is an existing acronym that cannot reasonably be justified, it should be eliminated, as I have requested in the past. For example, there should be no “HTS” [horizontal test stand] or “VTS” [vertical test stand] designations for test stands. Those are particularly dumb, as they contain unnecessary words. A “stand” at our test site is obviously a *test* stand. VTS-3 is four syllables compared with “Tripod,” which is two, so the bloody acronym version actually takes longer to say than the name! The key test for an acronym is to ask whether it helps or hurts communication. An acronym that most engineers outside of SpaceX already know, such as GUI, is fine to use. It is also ok to make up a few acronyms/contractions every now and again, assuming I have approved them, eg MVac and M9 instead of Merlin 1C-Vacuum or Merlin 1C-Sea Level, but those need to be kept to a minimum. This

There is a creeping tendency to use made up acronyms at SpaceX. Excessive use of made up acronyms is a significant impediment to communication and keeping communication good as we grow is incredibly important. Individually, a few acronyms here and there may not seem so bad, but if a thousand people are making these up, over time the result will be a huge glossary that we have to issue to new employees. No one can actually remember all these acronyms and people don’t want to seem dumb in a meeting, so they just sit there in ignorance. This is particularly tough on new employees. That needs to stop immediately or I will take drastic action—I have given enough warnings over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary. If there is an existing acronym that cannot reasonably be justified, it should be eliminated, as I have requested in the past. For example, there should be no “HTS” [horizontal test stand] or “VTS” [vertical test stand] designations for test stands. Those are particularly dumb, as they contain unnecessary words. A “stand” at our test site is obviously a *test* stand. VTS-3 is four syllables compared with “Tripod,” which is two, so the bloody acronym version actually takes longer to say than the name! The key test for an acronym is to ask whether it helps or hurts communication. An acronym that most engineers outside of SpaceX already know, such as GUI, is fine to use. It is also ok to make up a few acronyms/contractions every now and again, assuming I have approved them, eg MVac and M9 instead of Merlin 1C-Vacuum or Merlin 1C-Sea Level, but those need to be kept to a minimum.

KRAs and KPIs KRA and KPI are two confusing acronyms for an approach commonly recommended for identifying a person’s major job responsibilities. KRA stands for key result areas; KPI stands for key performance indicators. As academics and consultants explain this jargon, key result areas are the primary components or parts of the job in which a person is expected to deliver results. Key performance indicators represent the measures that will be used to determine how well the individual has performed. In other words, KRAs tell where the individual is supposed to concentrate her attention; KPIs tell how her performance in the specified areas should be measured. Probably few parts of the performance appraisal process create more misunderstanding and bewilderment than do the notion of KRAs and KPIs. The reason is that so much of the material written about KPIs and KRAs is both

EVA is an anachronistic term from the early days of spaceflight that dates back to the 1960s and has stuck over the years. EVA stands for Extravehicular Activity. Why it’s not an EA when extravehicular is one word baffles him. At a guess, acronyms sound better in threes. Technically, to conduct an EVA he uses an EMU or Extravehicular Mobility Unit, which, given the logic behind EVA should be an EVMU, but there’s nothing to be gained from swapping one cryptic acronym for another except one more entry in a dictionary. Mark

China operates the Lunar Permanent Astrobase Life-support Artificial Closed Ecosystem, or just the PALACE. Clearly, their acronym game is already equal to NASA's.

Agile thought leader Bill Wake created a set of guidelines for writing good user stories; to make them easier to remember, he uses the acronym INVEST: Independent: A good story should be independent of other stories. Stories shouldn't overlap in concept and should be implementable in any order. Negotiable: A good story isn't an explicit contract for features. The details for how a story's benefit will be delivered should be open to discussion. Valuable: A good story needs to be valuable to the customer. Estimable: A good story is one whose scope can be reasonably estimated. Small: Good stories tend to be small in scope. Larger stories will have greater uncertainty, so you should break them down.

Maybe we should have thought it strange for a student and her professor to go on a road trip, but you are only eight years older than I am, and you so often seem younger, even with all those acronyms after your name. Especially when you drove down Highway 9 in your red Mazda Miata with the top down, singing to Janis Joplin at the top of your lungs. I swear you didn’t care where we were going. You just loved the wind and the road, the sensation that we were moving somewhere.

Goals. OGTM uses this term to mean metrics of success. As metrics, goals should be fashioned as means of qualifying success at achieving an objective. Each goal needs to be SMART, an acronym that means Specific Measurable Actionable Realistic Time-constrained2