I need to put all of my networking protocol rants into one place for b̶o̶r̶i̶n̶g̶ ̶m̶u̶t̶u̶a̶l̶s̶ ̶t̶o̶ ̶d̶e̶a̶t̶h̶ ̶i̶n̶ ̶t̶h̶e̶ ̶D̶M̶s̶ easy access. Brace yourself:
How have I not tweeted anything about BGP? That seems unpossible - BGP's route table is the closest pre-existing analogue I can think of to the mempool...
Leaving these here b/c I typically mention them in the same arguments:
Tell me what you do at $DAYJOB writing software, and I'll tell you what food service industry job you'd be comfortable working at.
Thread!
You work at a nameless Fortune 500 company, churning out updates to the internal homegrown CRM software. You desperately want to leave but you have student loans to pay and this was the first temp-to-hire gig you could find.
You're working at McDonalds, and you effing hate it.
You work at a seed funded startup, desperately churning out code to grab more and more total addressable market share. You declined the Fortune 500 gig cuz you're cooler than that.
You'd be at a "hip" fast-casual spot like QDoba. You think it's better than McDonalds. It's not.
It's days like this I wonder - is it time for the ground up beetles, or the wheat poultices?
(Thread on how George Washington died. Mostly.)
On the evening of Dec 12, 1799, Washington came down with a nasty cough. It progressively worsened over the next 36 hours, until he woke up in the middle of the night on the 14th in severe respiratory distress.
The laypeople around him - the estate overseer and his personal secretary - first made him an elixir of molasses, vinegar and butter to treat his sore, swollen throat.
Was it the State that vouched for the money, or was it money that vouched for the State? On the Lydians vs. the Abbasids:
"...the sekka, the right of the ruler to have his name inscribed on coins, and the ḵoṭba, his right to have his name mentioned in the sermon at the congregational worship service on Friday, were the two formal prerogatives of sovereignty....."
Tired: when the money vouches for your head of state
Wired: when the money vouches for your prophet
Constantinople vs. Caliph Abd'Al-Malik in the coin wars:
"Layering has both technical and social implications: it makes the technical complexity of the system more manageable, and it allows the system to be designed and built in a decentralized way."
How layering made building the ARPANet possible:
"The ARPANET was born from an inspiration and a need..." Depending on who you ask, the ARPANet was built to enable time-sharing of remote compute resources, or a military command-and-control capability that could withstand nuclear attack, or - my fave - man-computer symbiosis.
Fun fact: AT&T could have taken over the ARPANet in the late 60s, but "...there was no place for equipment or procedures that might unbalance the intricate technical and bureaucratic arrangements that AT&T executives had put into place..." (!)
"Broad social trends, roughly what an economist would call "network externalities," play a significant part in the adoption of one technology over another. I contend that ... the Web did not overshadow Gopher simply based on the technical qualities of HTTP as a protocol."
"In order for complex systems to perpetuate... they must strike the balance between exploring new options and exploiting past success... [and] make new advances to fill new niches that arise w/o changing so radically that they can no longer take advantage of their track record."