A few years back, we had to get our front porch replaced. It was starting to tilt and the rail felt very flimsy. We got an estimate of the scope of work, approved it, and...
... the workers immediately found out that the columns supporting the roof were just empty cladding.
The team lost a few days to this, scrambling to stabilize the roof over the porch. They took apart the front railing and found that there was a single piece of years-old, pressure-treated wood holding up one entire side of the porch & roof. It was not anchored to the ground.
Mar 13, 2022 • 4 tweets • 1 min read
what was I programming when I drew this?
I have maybe 2-3 guesses.
May 27, 2020 • 5 tweets • 1 min read
I want to expand on this a bit – there have long been folks doing an incredible amount of work on Node to onboard new contributors, seek consensus, etc. The project survives on their work, which is incredibly emotionally draining.
The project should _not_ demand that much out of contributors. As is, it'll consume your every waking moment trying to drive contentious topics to consensus – and you still might end up with a lemon!
Dec 4, 2019 • 43 tweets • 8 min read
there's a lot to like here, I.. might live tweet as I go through it
Section 5: Taxonomy: Faults vs. Errors – I appreciate how they've separated out the two classes of errors (faults affect availability, errors do not.) Also, the metrics recommendations here are spot-on re: latency vs overall time-to-complete long-running operations.
Jan 23, 2019 • 9 tweets • 2 min read
would anyone be interested in a brief explanation of the flow of API requests for a npm package install, or is this already general knowledge?
okay, I'll write this up in a larger form elsewhere, later, but: no time like the present and no... medium... like... the twitter feed, I suppose
Jan 22, 2019 • 13 tweets • 2 min read
one of the fascinating things about "coders at work" is being transported back to 2009 and seeing the preoccupation with "our multicore future" at the time
and then looking at the present day and connecting dots.
my hot take^W^Wread is that:
- python, ruby, js, and java are "of a generation" of programming languages (say: 3rd gen)
- well-resourced companies went heads down and sought to address 2nd/3rd gen issues with a new generation of PLs
- meanwhile, js
