Tripod Stand 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.

But this isn't standard Japanese picnic fare: not a grain of rice or a pickled plum in sight. Instead, they fill the varnished wooden tables with thick slices of crusty bread, wedges of weeping cheese, batons of hard salamis, and slices of cured ham. To drink, bottles of local white wine, covered in condensation, and high-alcohol microbews rich in hops and local iconography. From the coastline we begin our slow, dramatic ascent into the mountains of Hokkaido. The colors bleed from broccoli to banana to butternut to beet as we climb, inching ever closer to the heart of autumn. My neighbors, an increasingly jovial group of thirtysomethings with a few words of English to spare, pass me a glass of wine and a plate of cheese, and I begin to feel the fog dissipate. We stop at a small train station in the foothills outside of Ginzan, and my entire car suddenly empties. A husband-and-wife team has set up a small stand on the train platform, selling warm apple hand pies made with layers of flaky pastry and apples from their orchard just outside of town. I buy one, take a bite, then immediately buy there more. Back on the train, young uniformed women flood the cars with samples of Hokkaido ice cream. The group behind me breaks out in song, a ballad, I'm later told, dedicated to the beauty of the season. Everywhere we go, from the golden fields of empty cornstalks to the dense forest thickets to the rushing rivers that carve up this land like the fat of a Wagyu steak, groups of camouflaged photographers lie in wait, tripods and shutter releases ready, hoping to capture the perfect photo of the SL Niseko steaming its way through the hills of Hokkaido.

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.

It's barely 8:00 a.m., but my train mates waste little time in breaking out the picnic material. But this isn't standard Japanese picnic fare: not a grain of rice or a pickled plum in sight. Instead, they fill the varnished wooden tables with thick slices of crusty bread, wedges of weeping cheese, batons of hard salamis, and slices of cured ham. To drink, bottles of local white wine, covered in condensation, and high-alcohol microbews rich in hops and local iconography. From the coastline we begin our slow, dramatic ascent into the mountains of Hokkaido. The colors bleed from broccoli to banana to butternut to beet as we climb, inching ever closer to the heart of autumn. My neighbors, an increasingly jovial group of thirtysomethings with a few words of English to spare, pass me a glass of wine and a plate of cheese, and I begin to feel the fog dissipate. We stop at a small train station in the foothills outside of Ginzan, and my entire car suddenly empties. A husband-and-wife team has set up a small stand on the train platform, selling warm apple hand pies made with layers of flaky pastry and apples from their orchard just outside of town. I buy one, take a bite, then immediately buy three more. Back on the train, young uniformed women flood the cars with samples of Hokkaido ice cream. The group behind me breaks out in song, a ballad, I'm later told, dedicated to the beauty of the season. Everywhere we go, from the golden fields of empty cornstalks to the dense forest thickets to the rushing rivers that carve up this land like the fat of a Wagyu steak, groups of camouflaged photographers lie in wait, tripods and shutter releases ready, hoping to capture the perfect photo of the SL Niseko steaming its way through the hills of Hokkaido.

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

We have been dreaming of robots since Homer. In Book 18 of the Iliad , Achilles’ mother, the nymph Thetis, wants to order a new suit of armor for her son, and so she pays a visit to the Olympian atelier of the blacksmith-god Hephaestus, whom she finds hard at work on a series of automata: . . . He was crafting twenty tripods to stand along the walls of his well-built manse, affixing golden wheels to the bottom of each one so they might wheel down on their own [automatoi] to the gods’ assembly and then return to his house anon: an amazing sight to see. These are not the only animate household objects to appear in the Homeric epics. In Book 5 of the Iliad we hear that the gates of Olympus swivel on their hinges of their own accord, automatai , to let gods in their chariots in or out, thus anticipating by nearly thirty centuries the automatic garage door. In Book 7 of the Odyssey , Odysseus finds himself the guest of a fabulously wealthy king whose palace includes such conveniences as gold and silver watchdogs, ever alert, never aging. To this class of lifelike but intellectually inert household helpers we might ascribe other automata in the classical tradition. In the Argonautica of Apollonius of Rhodes, a third-century-BC epic about Jason and the Argonauts, a bronze giant called Talos runs three times around the island of Crete each day, protecting Zeus’s beloved Europa: a primitive home alarm system.

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.

When Arizona emerged from dry dock with new steel plates welded into place on the portside blister to close the gash from the collision, there was a far more noticeable and ominous change in the ship’s appearance. The Navy’s peacetime color scheme of light gray had given way to a dark bluish-gray applied to the hull and superstructure up to the level of the bridge. Only the foretop and maintop enclosures on the two tripod masts and the tops of the masts themselves were still light gray. This was a form of wartime camouflage that supposedly made the ship less likely to stand out against the horizon.

Careful," Janet exclaimed sharply, as Lara's heavy skirts brushed the side of a glass bowl set in a tripod mahogany stand, causing it to wobble. Lara glanced down at the forlorn pair of goldfish swimming in the bowl, and then back at Janet's pinched, narrow face. "They shouldn't be placed in the window," Lara heard herself murmur. "They don't like too much light.

Language systems stand on a tripod. There's the language, there's the libraries, and there are the tools. And how successful a language is depends on a complex interaction between those three things.

Another badass Gurkha in recent memory was Sergeant Dipprasad Pun of the Royal Gurkha Rifles. In 2010, while serving as the lone on-duty guard patrolling a small one-room outpost on the edge of the Afghan province of Helmand, Pun was suddenly ambushed by somewhere between fifteen and thirty Taliban warriors armed with RPGs and assault rifles. During his Ultimate Mega Gurkha Freakout Limit Break Mode, the five-foot-seven-inch sergeant fired off four hundred rounds of machine gun ammunition (every bullet he had), chucked seventeen grenades, detonated a remote mine, and then took an enemy soldier down by chucking a twenty-pound machine gun tripod into the dude’s face.