189
" When Musk announced in 2014 that Tesla would open-source all of its patents, analysts tried to decide whether this was a publicity stunt or if it hid an ulterior motive or a catch. But the decision was a straightforward one for Musk. He wants people to make and buy electric cars. Man’s future, as he sees it, depends on this. If open-sourcing Tesla’s patents means other companies can build electric cars more easily, then that is good for mankind, and the ideas should be free. The cynic will scoff at this, and understandably so. Musk, however, has been programmed to behave this way and tends to be sincere when explaining his thinking—almost to a fault. "
― Ashlee Vance , Elon Musk: Tesla, SpaceX, and the Quest for a Fantastic Future
193
" 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. "
― Ashlee Vance , Elon Musk: Tesla, SpaceX, and the Quest for a Fantastic Future
