colleague: My housemate would throttle me if anything bad happens to our beloved porcelain bowl
me: You mean like reduce the number of times you can use kitchen equipment per time period? 🤓
At the time, my understanding of the word "throttle" involved two concepts. The first is the car pedal that a driver steps on to make a vehicle go faster. The second is what a web service does to prevent a client from overwhelming it with too many requests.
This exchange prompted me to look up the actual meaning of throttle: to choke, suffocate or strangle, which was what my colleague was pleading us to prevent from happening. I'm pretty sure this definition predates its use in automobiles and web requests.
To throttle a web request, I understand. The more severe the throttling, the fewer requests get through. Throttle in the context of the car pedal though is less intuitive because stepping on it allows more fuel into the engine, making the vehicle travel faster.
Turns out the term comes from the throttle valve in a combustion engine. The default state is for the valve to be at its most constricted or "throttled" (just enough for the engine to keep running). Stepping on the accelerator pedal "unthrottles" the valve, allowing more fuel to flow into the engine.
So really, calling the pedal the "accelerator" is accurate, but in terms of "throttle", it should be the "unthrottle" pedal. Also when someone dramatically declares "hit the throttle" with the intention of making their vehicle go faster, what they really mean is "hit the unthrottle" 😂.
Just finished reading Promise Me, Dad. Easy, enjoyable, emotionally-rich read. It was a refreshing departure from Capitalism without Capital which was quite academic and An Elegant Puzzle which was quite task-focused.
The thing that stood out most prominently to me is how much time Joe and staff spend strategising, writing speeches, delivering speeches, setting up meetings and calls and corraling people.
In the last month or so, I've been gradually removing myself from the implementation and deployment of code within the team. Instead, I've been focusing on establishing robust processes, streamlining communication flow and information dissemination, and listening intensely to where each member on the team is at, helping to unstick things that are missed in the macro movement of things.
The contours of such efforts differ dramatically from that of an individual contributor. As an individual contributor, I spend my days cracking the back of engineering problems, coding up the solution, considering tests, stepping through deployment environments and seeing it operational in the hands of customers. There is a cadence to it that is irrefutable. I feel confident, safe, satisfied.
Of late, my son would ask me - how was your day? What did you do at work? My answer has been consistently vague - I talk to people, I have meetings, I sometimes solve puzzles.
Feels less irrefutable.
Reading about the strategising, the speech-ing, the people corraling affirmed me that the activities that fill my workday, albeit at a far smaller scale than that of a VPOTUS, have inherant value that I've still yet to fully embrace.
One day I would like to have mustered up the conviction to explain to my son: people long to accomplish things that are much greater than themselves. In order to achieve that, they need to find ways to work with each other. Everyday, daddy has the opportunity to help people do that at work.
Let's take the conversation to mastodon.
Tooting has gone quite well. I'm running my own instance, learning the ins and outs of mastodon administration. I've managed to stand up elasticsearch for it, and I've now reached semi-pro level live-tooting-while-reading. Check out my toots for An Elegant Puzzle #aep19 and Capitalism without Capital #cwoc19. Riveting stuff.
I must be on a roll.
To take advantage of this self-publishing momentum, I've spent the last two nights trying to revive this ol'blog.
Night one was spent trying to upgrade to the latest version 3.x, because new is supposedly good. Apparently not so good for me because a bunch of the APIs have changed, which caused my heavily customised theme to break. Oh well, worth the try. A simple
git checkout <old branch> and we were back.
(I'd been doing all of this via
ssh on the live server)
Night two, I figured I'd skip the upgrade and appease myself with a slight polish of the theme. The latency of
emacs-ing live on the server was too painful, so I thought my Surface Go is a real computer right? Brought up Ubuntu in Windows 10, installed
php7.2-cli and friends, then
php -S 127.0.0.1:8080. Just like that, I was off tweaking markup/styles,
alt-tab, ctrl-R, repeat.
It's been so long since I've tweaked HTML and CSS, it brought back fond memories of recording
vim macros to automate HTML tag transform operations. Ah my youth.
It worked. I'm most proud of the fact that all this was done on a supposedly underpowered Pentium 1.6GHz chip with a paltry 4GB of RAM, both of which get largely chewed up by some
Antimalware Service Executable.
I'm going to write more. I'll try. This was actually fun.
It's a little roundabout at the moment, but if you feel an overwhelming urge to respond, you may do so on this toot. You will have my appreciation.
The engineering team at Sidekicker recently moved to a fully containerised approach to deploying software. I thought it would be a good idea to write about why we did it, and how it sets us up for the long run.
…part of the power of the social media business model is that it introduces a type of attention collectivism, where I’ll promise to pretend to care what you have to say (by clicking “like” or leaving a quick comment), if you do the same for me. This is incredibly seductive, though ultimately hollow.
— Cal Newport
This is harrowingly pertinent now that I've shared my very first blog post on LinkedIn. It's hard to tell how well the post is received on my actual site, but I'm glued to the 👍 Like count on LinkedIn. 😩