I hereby claim:
- I am pavelpascari on github.
- I am pascaripavel (https://keybase.io/pascaripavel) on keybase.
- I have a public key ASAxq5WSm8kFbWmW2IVS-CCI7NHo3Rssl6fMZLDw2Q5FjQo
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
import axios, { AxiosRequestConfig } from "axios"; | |
import router from "@/router"; //shortcut to src | |
import { Module } from "vuex"; | |
const authModule: Module<any, any> = { | |
state: { | |
loggedIn: false, | |
loginError: null, | |
username: null |
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 warning over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary.
<h1>Hello FAF, this is a document</h1> | |
<p>So we're trying to do interesting documents</p> | |
<p>They are actually quide <strong>hard</strong> | |
Not that <em>easy</em></p> | |
<p>What happens if we do ##this?</p> | |
<p>How about <code><em>this</strong></em>?</p> |