Standard escape codes are prefixed with Escape:
- Ctrl-Key:
^[ - Octal:
\033 - Unicode:
\u001b - Hexadecimal:
\x1B - Decimal:
27
| Bofa Rush Ironman v1.4 by Kirbuti (last update: 28 July 2023) | |
| Section 0: Setup/General notes | |
| This guide is designed to prioritize: | |
| 1. Rushing 43 Prayer while as low of a combat level as possible, | |
| 2. Obtaining barrows gloves, | |
| 3. Completing Song of the Elves immediately afterwards, | |
| 4. Begin completing Corrupted Gauntlet with stats that are reasonable to do so |
This content moved here: https://exploringjs.com/impatient-js/ch_arrays.html#quickref-arrays
package.json, set version to a prerelease version, e.g. 2.0.0-rc1, 3.1.5-rc4, ...npm pack to create packagenpm publish <package>.tgz --tag next to publish the package under the next tagnpm install --save package@next to install prerelease package| # Get a file from a repo on github | |
| TOKEN=$GITHUB_TOKEN | |
| OWNER=$1 | |
| REPO=$2 | |
| PATH=$3 | |
| FILE="https://api.github.com/repos/$OWNER/$REPO/contents/$PATH" | |
| /usr/bin/curl -v --header "Authorization: token $TOKEN" \ | |
| --header 'Accept: application/vnd.github.v3.raw' \ |
People
:bowtie: |
๐ :smile: |
๐ :laughing: |
|---|---|---|
๐ :blush: |
๐ :smiley: |
:relaxed: |
๐ :smirk: |
๐ :heart_eyes: |
๐ :kissing_heart: |
๐ :kissing_closed_eyes: |
๐ณ :flushed: |
๐ :relieved: |
๐ :satisfied: |
๐ :grin: |
๐ :wink: |
๐ :stuck_out_tongue_winking_eye: |
๐ :stuck_out_tongue_closed_eyes: |
๐ :grinning: |
๐ :kissing: |
๐ :kissing_smiling_eyes: |
๐ :stuck_out_tongue: |
Sometimes you want to have a subdirectory on the master branch be the root directory of a repositoryโs gh-pages branch. This is useful for things like sites developed with Yeoman, or if you have a Jekyll site contained in the master branch alongside the rest of your code.
For the sake of this example, letโs pretend the subfolder containing your site is named dist.
Remove the dist directory from the projectโs .gitignore file (itโs ignored by default by Yeoman).
| -- show running queries (pre 9.2) | |
| SELECT procpid, age(clock_timestamp(), query_start), usename, current_query | |
| FROM pg_stat_activity | |
| WHERE current_query != '<IDLE>' AND current_query NOT ILIKE '%pg_stat_activity%' | |
| ORDER BY query_start desc; | |
| -- show running queries (9.2) | |
| SELECT pid, age(clock_timestamp(), query_start), usename, query | |
| FROM pg_stat_activity | |
| WHERE query != '<IDLE>' AND query NOT ILIKE '%pg_stat_activity%' |
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