| /* | |
| Copy this into the console of any web page that is interactive and doesn't | |
| do hard reloads. You will hear your DOM changes as different pitches of | |
| audio. | |
| I have found this interesting for debugging, but also fun to hear web pages | |
| render like UIs do in movies. | |
| */ | |
| const audioCtx = new (window.AudioContext || window.webkitAudioContext)() |
| " cat | |
| lac 017777 i " Load accumulator (AC) with argument count | |
| sad d4 " Skip next if we have more than 4 words of args | |
| jmp nofiles " Otherwise, jump to nofiles | |
| lac 017777 " Load AC with address of args | |
| tad d1 " Increment AC by 1, past argument count | |
| tad d4 " Increment AC by 4, now AC points to first real arg | |
| dac name " Save arg pointer from AC into 'name' |
| # Delete all containers | |
| docker rm $(docker ps -aq --filter status="exited" --filter status="dead") | |
| docker rm $(docker ps -aq) | |
| # Delete all untaged images | |
| docker rmi $(docker images --filter "dangling=true" -q | sort -u) | |
| http://serverspec.org/resource_types.html | |
| https://docs.docker.com/engine/installation/linux/ubuntulinux/#create-a-docker-group |
| var crypto = require('crypto'); | |
| // larger numbers mean better security, less | |
| var config = { | |
| // size of the generated hash | |
| hashBytes: 32, | |
| // larger salt means hashed passwords are more resistant to rainbow table, but | |
| // you get diminishing returns pretty fast | |
| saltBytes: 16, | |
| // more iterations means an attacker has to take longer to brute force an |
I frequently administer remote servers over SSH, and need to copy data to my clipboard. If the text I want to copy all fits on one screen, then I simply select it with my mouse and press CMD-C, which asks relies on m y terminal emulator (xterm2) to throw it to the clipboard.
This isn't practical for larger texts, like when I want to copy the whole contents of a file.
If I had been editing large-file.txt locally, I could easily copy its contents by using the pbcopy command:
| # Sublime Text 3 languages list: | |
| ls -1 /Applications/Sublime\ Text.app/Contents/MacOS/Packages/ | |
| # Remove all default Sublime Text 3 snippets for Python language | |
| export ST3_LANG="Python" | |
| mkdir -p ~/Library/Application\ Support/Sublime\ Text\ 3/Packages/$ST3_LANG/ | |
| unzip -l /Applications/Sublime\ Text.app/Contents/MacOS/Packages/$ST3_LANG.sublime-package | grep '.sublime-snippet' | awk '{print $4}' | while read f; do touch ~/Library/Application\ Support/Sublime\ Text\ 3/Packages/$ST3_LANG/$f; done | |
| unset ST3_LANG |
| FROM ubuntu | |
| MAINTAINER Eric Mill "eric@konklone.com" | |
| # turn on universe packages | |
| RUN echo "deb http://archive.ubuntu.com/ubuntu raring main universe" > /etc/apt/sources.list | |
| RUN apt-get update | |
| # basics | |
| RUN apt-get install -y nginx openssh-server git-core openssh-client curl | |
| RUN apt-get install -y nano |
| // Just before switching jobs: | |
| // Add one of these. | |
| // Preferably into the same commit where you do a large merge. | |
| // | |
| // This started as a tweet with a joke of "C++ pro-tip: #define private public", | |
| // and then it quickly escalated into more and more evil suggestions. | |
| // I've tried to capture interesting suggestions here. | |
| // | |
| // Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_, | |
| // @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant, |
| // I needed flatuicolors.com as Sass variables... | |
| // In your console, run: | |
| $('.color').get().map(function(el) { return "$" + el.classList[1] + ": " + el.getAttribute('data-clipboard-text') + ';' }).join('\r\n'); | |
| // Output: | |
| // $turquoise: #1abc9c; | |
| // $emerland: #2ecc71; | |
| // $peter-river: #3498db; | |
| // $amethyst: #9b59b6; | |
| // $wet-asphalt: #34495e; |
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