meangrape

1 pound bucatini or similarly thick pasta (spaghetti in times of need;
   cacio e pepe needs thick sturdy pasta)
4 ounces (~2 cups) of pecorino romano finely grated
   (or gran padano or parmigiano reggiano depending on what you can find)
3 TB olive oil
1 TB butter
Black pepepr (freshly ground)

You need two pans. I use a 12" frying pan and a 3qt saucier.
You can replace the saucier with another large frying pan.

meangrape

For cooking
===========
Oil (not olive -- just plain old canola or vegetable of something)
2 white or yellow onions cut in half
3" of ginger sliced (no need to peel)
2-4 star anise
1 cinammon stick
4 cloves
1TB fennel seeds
1TB coriander seeds

meangrape

# GIT heart FZF
# -------------

is_in_git_repo() {
  git rev-parse HEAD > /dev/null 2>&1
}

fzf-down() {
  fzf --height 50% "$@" --border
}

meangrape

+ trap __exit_cleanup EXIT INT                                                                                                                               
+ ps -a -o pid,args                                                                                                                                          
+ grep 89355                                                                                                                                                 
+ grep -v grep                                                                                                                                               
+ tr -s ' '                                                                                                                                                  
+ cut -d ' ' -f 3                                                                                                                                            
+ CALLER=-                                                                  

meangrape

2017/10/03 18:07:16 [INFO] Terraform version: 0.10.7  
2017/10/03 18:07:16 [INFO] Go runtime version: go1.9
2017/10/03 18:07:16 [INFO] CLI args: []string{"/usr/local/bin/terraform", "plan"}
2017/10/03 18:07:16 [DEBUG] Attempting to open CLI config file: /home/jayed/.terraformrc
2017/10/03 18:07:16 [DEBUG] File doesn't exist, but doesn't need to. Ignoring.
2017/10/03 18:07:16 [DEBUG] CLI Config is main.Config{Providers:map[string]string{}, Provisioners:map[string]string{}, DisableCheckpoint:false, DisableCheckpointSignature:false, PluginCacheDir:""}
2017/10/03 18:07:16 [INFO] CLI command args: []string{"plan"}
2017/10/03 18:07:16 [INFO] command: empty terraform config, returning nil
2017/10/03 18:07:16 [DEBUG] command: no data state file found for backend config
2017/10/03 18:07:16 [DEBUG] New state was assigned lineage "2c37d4ad-bfcd-4db5-b26e-eeb9919660c9"

meangrape

12" flour tortilla
6-8 slices of pastrami
Sauerkraut
1-2 fried eggs
Ghost pepper garlic sausage (cooked)
10-12 crispy tater tots
Chili sauce (with onions and beef not that weird heinz stuff in a jar)
Pickled jalapeño
Sliced habanero (deseeded)
Nacho cheese sauce

meangrape

Keybase proof

I hereby claim:

• I am jayed on github.
• I am meangrape (https://keybase.io/meangrape) on keybase.
• I have a public key ASD-bZjJUO3B8ACGltc_9e01_NtAZ_vMSMrjAC8QWJ-lPQo

To claim this, I am signing this object:

meangrape

2L H2O bladder
Water purification tablets (plus instructions)
Magnesium + scraper + flint
Stormproof matches
Wet Fire tinder
24 chemlights
1 ultralight medical kit
200' 550 cord
Leatherman multitool
Milspec compass

meangrape

The problem I have with the term technical debt is that 
people retroactively declare it.

It's one thing to have good technical debt – a conscious
decision to put off work (like upgrading your database schema) 
knowing that it would help you now, but believing that you need to 
direct that effort elsewhere. 

It's another thing to have bad technical debt 
(similar to a payday loan) by implementing a stupid

meangrape

Generously, we had three database servers and maybe forty application/web servers at the time. This was the default view of every other user.

If a user, U, clicked on another user, U' we would:
(a) get the list of followers from U', F'
(b) determine if any of the people in F' were protected
    (1) determine if those protected users allowed user U to see their tweets or not
(c) get the last X tweets from each user in F' that U could see and compose them into a timeline

We didn't look at the users that might be visible on a page of tweets we did the intersection against all the followers.
We didn't cache any of the allowed-viewing-relationship information; it was computed every time directly from the databases any time a user clicked on any other user's page. So the result was a view of the user's timeline MINUS any tweets that belonged to protected users that you didn't follow.