- local development workflow
- ensure there's a dev branch that matches the machine ID and force schema, truncate tables, load dev data, write branch name/access keys to envs
- ensure there's a test branch that matches the machine ID and force schema, truncate tables, write branch name/access keys to envs
- github branch workflow
- ensure there's a test branch that matches 'github', branch_name, and force schema, truncate data, write branch name/access keys to envs
- deployment workflows
- deploying to staging, create a branch off of staging if schema changed, force schema, try to merge, block code deploy if you can't merge
- deploying to production, create a branch off of production if schema changed, force schema, try to merge, block code deploy if you can't merge
[package] | |
name = "hackerchat-rust" | |
version = "0.1.0" | |
edition = "2021" | |
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html | |
[dependencies] | |
anyhow = "1.0.69" | |
async-channel = "1.8.0" |
package main | |
import ( | |
"bufio" | |
"encoding/json" | |
"fmt" | |
"net" | |
"os" | |
"sync" | |
"time" |
export interface SpacePacketHeader { | |
versionNumber: string | number | |
identification: { | |
apid: number | |
secondaryHeader: number | |
type: number | |
} | |
sequenceControl: { | |
packetName: number | |
sequenceFlags: number |
alias gb='gh pr view -w' | |
alias gp='git push origin HEAD' | |
alias gpf='git push --force-with-lease origin HEAD' | |
alias gpfo='git push --force-with-lease origin HEAD && gb' | |
alias gpo='git push origin HEAD && gb' | |
alias gcm='git checkout $(git_detect_main_branch)' | |
alias gcmp='git checkout $(git_detect_main_branch) && git pull origin $(git_detect_main_branch) --ff-only' | |
alias grom='git fetch && git rebase --autostash origin/$(git_detect_main_branch)' | |
function git_detect_main_branch() { |
const slugifyP = import('@sindresorhus/slugify') | |
slugifyP.then(slugify => console.log(slugify.default('I ♥ Dogs'))) |
import { buildFunctions, findFunctions } from './lib-build' | |
async function run() { | |
const funcs = await findFunctions() | |
await buildFunctions(funcs) | |
} | |
run() |
type AsyncFuncReturn<T> = T extends (...args: any[]) => Promise<infer U> ? U : never | |
// eg | |
const randomFunction = async () => ({ a: 4, b: "string" }) | |
type RandomReturn = AsyncFuncReturn<typeof randomFunction> | |
const foo: RandomReturn = await randomFunction() |
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