⌘T | go to file |
⌘⌃P | go to project |
⌘R | go to methods |
⌃G | go to line |
⌘KB | toggle side bar |
⌘⇧P | command prompt |
Locate the section for your github remote in the .git/config
file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = git@github.com:joyent/node.git
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/*
to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:
{ | |
"comment": "This is the settings file for the SVGO Compressor Plugin. For more info, please check <https://github.com/BohemianCoding/svgo-compressor>", | |
"pretty": false, | |
"indent": 2, | |
"plugins": [ | |
{ | |
"name": "cleanupAttrs" | |
}, | |
{ | |
"name": "cleanupEnableBackground" |
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.
One of the biggest pain point for users in ethereum:
- users don't want to think about ether
- users don't want to think about backing up private keys or seed phrases
- users need to set up 2 factor authentication to be secure
- users want to be able to have a simple identifiable username
- users want to be able to pay for transactions using what they already have on the system, be apple pay, xbox points or even a credit card
- users want to use the same username accross multiple devices in a trustless manner
import SwiftUI | |
extension Color { | |
static var background: Color { | |
return Color(uiColor: .systemBackground) | |
} | |
static var secondaryBackground: Color { | |
return Color(uiColor: .secondarySystemBackground) | |
} |