Written by @trgwii, not me:
"If Go wasn't made by Google, what would be bad about it?" Stafn asked.
And this is the response from Thomas:
- uncomposable error handling, this is like being back to:
I get asked pretty regularly what my opinion is on merge commits vs rebasing vs squashing. I've typed up this response so many times that I've decided to just put it in a gist so I can reference it whenever it comes up again.
I use merge, squash, rebase all situationally. I believe they all have their merits but their usage depends on the context. I think anyone who says any particular strategy is the right answer 100% of the time is wrong, but I think there is considerable acceptable leeway in when you use each. What follows is my personal and professional opinion:
Learn how to send emails through Gmail SMTP with Cloudflare Email Routing in this comprehensive guide.
To proceed with this method, ensure that you have enabled two-factor authentication for your Google account. If you haven't done so already, you can follow the link to set it up → Enable 2FA in your Google account.
provider "aws" { | |
version = "~> 2.0" | |
region = "eu-west-2" | |
} | |
# Providing a reference to our default VPC | |
resource "aws_default_vpc" "default_vpc" { | |
} | |
# Providing a reference to our default subnets |
## ZSH Options | |
# http://zsh.sourceforge.net/Doc/Release/Options.html | |
# Changing Directories | |
# http://zsh.sourceforge.net/Doc/Release/Options.html#Changing-Directories | |
setopt auto_cd # if a command isn't valid, but is a directory, cd to that dir | |
setopt auto_pushd # make cd push the old directory onto the directory stack | |
setopt pushd_ignore_dups # don’t push multiple copies of the same directory onto the directory stack | |
setopt pushd_minus # exchanges the meanings of ‘+’ and ‘-’ when specifying a directory in the stack |
I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.
I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real
The following instructions describe a set of processes allowing you to run Django database migrations against a production database without having to bring the web service down.
Note that in the below instructions, migrations are all run manually at explicit points, and are not an automatic part of the deployment process.
from collections import namedtuple | |
class Money(namedtuple('Money', ['amount', 'currency'])): | |
def add(self, amount): | |
return Money(self.amount + amount, self.currency) | |
m = Money(20, 'USD') | |
print(m) | |
# Money(amount=20, currency='USD') |