14 Matching Annotations
  1. Oct 2026
    1. When he saw that I couldn't open the door I asked him what the trick was he said, in a tone of voice that made it sound like this was obviously something everyone should know, you need to pull the door before pushing it. The door was wedged such that the easiest way to open the door was to pull the door as tightly shut as possible and then immediately shove the door open. This friend, since he grew up in that house, thought this was obvious, apparently not realizing that it's not normal to have to try to close a door extra hard to open it.

      This "missing stairstep" analogy is appropriate here, though that metaphor is most commonly associated with a very specific type of problem involving guys who are creeps.

      As it relates to the broader context of technology that this piece situates this anecdote within, it could be considered a form of implicit step zero or an analogy for developer tunnel vision.

  2. Mar 2026
  3. Feb 2026
    1. The most popular static site generator, Jekyll, may have the best documentation pages of the lot. And yet, it still puts a bunch of technical language front-and-center, on the project’s home page: Jekyll’s core message, “Get up and running in seconds” This is developer-talk, because static site generators are tools made by developers for themselves and their peers.

      This is the prime example I use to illustrate implicit step zero.

  4. Aug 2024
    1. Written inPython, Cython

      Is this accurate? I don't have a lot of firsthand experience with data science stuff, but usually when looking just past surface-level you find that some Python package is really a shell around some native binary core implemented in e.g. C (or Fortran?).

      When I at the repos for spaCy and its assistant Thinc, GitHub's language analysis shows that it's pretty much Python. Is there something lurking in the shadows that I'm not seeing? Or does this mean that if someone cloned spaCy and Thinc and wrote it in JS, then the subset of data scientists whose work can be done with those two packages (and whatever datavis generators they use) will benefit from the faster runtime and the the elimination of figging and other setup?

  5. Nov 2023
  6. May 2022
    1. okay how about ruby? oh I have old ruby , hmmm , try to install new ruby, seems to run, but it can't find certain gems or something. oh and this other ruby thing I was using is now broken ? why do I have to install this stuff globally? You don't but there are several magic spells you must execute and runes you must set in the rigtt places.
    1. But… on installing node.js you’re greeted with this screen (wtf is user/local/bin in $path?), and left to fire up the command line.

      Agreed. NodeJS is developer tooling. It's well past the time where we should have started packaging up apps/utilities that are written in JS so that they can run directly in* the browser—instead of shamelessly targeting NodeJS's non-standard APIs (on the off-chance everyone in your audience is a technical user and/or already has it installed).

      This is exactly the crusade I've been on (intermittently) when I've had the resources (time/opportunity) to work on it.

      Eliminate implicit step zero from software development. Make your projects' meta-tooling accessible to all potential contributors.

      * And I do mean "in the browser"—not "on a server somewhere that you are able to use your browser to access, à la modern SaaS/PaaS"

  7. Mar 2022
  8. Sep 2021