4 ms·

It got the point where they had to justify what they were saying, but realised they were using circular reasoning (great software is great because it’s great).

It got the point where they had to justify what they were saying, but realised they were using circular reasoning (great software is great because it’s great). So they just gave up and hit Submit.

hiAndrewQuinn 2y ago
I might have buried the lede a little too deep. Mea maxima culpa. This is what I get for not listening to the maxim "Use More Examples. Yes, Even More Than That." Let me start to plug that hole now. The concrete example I was thinking of while writing this was Bram Moolenaar's `vim` (RIP). I'm pretty sure most people would argue `vim` is great software in at least some abstract sense, even if they are ride-or-die for Emacs or Kakoune or some such. Plenty of `vi` clones already existed by the time Bram started work on `vim` in '91. That gives us the community, scene, subscene layering I suggest. The pool of text editor users is massive worldwide; text editor power users are smaller in number but still quite large; and text editor creators are smaller still but tend to be very enthusiastic about their craft. How do we know Bram was a member of all 3 groups? Well, he has a page literally titled "Seven habits of effective text editing" [1], which isn't even really specific to Vim -- it just outlines the beliefs that have crystallized for him over a long, long lifetime of editing text really, really well. It also means that `vim` did not spring fully formed from the forehead of Bram. There was a whole litany of iterations going on at the time which he could tap into, previous riffs on the genre that were successful, but could have been even moreso. Other software I would put in this camp might be: Linux, Obsidian, Podman, Kubernetes (kinda - you really have to run into all of those SRE problems individually before you can arrive at a design like k8s, and even then there are things most people agree could be improved upon). They all have this iterative pattern to them, kind of like dogfooding to the max.
- syndicatedjelly 2y ago
  Thanks for taking that feedback in stride. I like your example of vim, and how Bram drew from a wealth of experience - not just in software - to inform his decisions for vim. I'd love to see you discuss that example in the original article, and maybe even some more from the list. THAT would be a compelling article.

It got the point where they had to justify what they were saying, but realised they were using circular reasoning (great software is great because it’s great). So they just gave up and hit Submit.

hiAndrewQuinn 2y ago

I might have buried the lede a little too deep. Mea maxima culpa. This is what I get for not listening to the maxim "Use More Examples. Yes, Even More Than That." Let me start to plug that hole now. The concrete example I was thinking of while writing this was Bram Moolenaar's `vim` (RIP). I'm pretty sure most people would argue `vim` is great software in at least some abstract sense, even if they are ride-or-die for Emacs or Kakoune or some such. Plenty of `vi` clones already existed by the time Bram started work on `vim` in '91. That gives us the community, scene, subscene layering I suggest. The pool of text editor users is massive worldwide; text editor power users are smaller in number but still quite large; and text editor creators are smaller still but tend to be very enthusiastic about their craft. How do we know Bram was a member of all 3 groups? Well, he has a page literally titled "Seven habits of effective text editing" [1], which isn't even really specific to Vim -- it just outlines the beliefs that have crystallized for him over a long, long lifetime of editing text really, really well. It also means that `vim` did not spring fully formed from the forehead of Bram. There was a whole litany of iterations going on at the time which he could tap into, previous riffs on the genre that were successful, but could have been even moreso. Other software I would put in this camp might be: Linux, Obsidian, Podman, Kubernetes (kinda - you really have to run into all of those SRE problems individually before you can arrive at a design like k8s, and even then there are things most people agree could be improved upon). They all have this iterative pattern to them, kind of like dogfooding to the max.

syndicatedjelly 2y ago
Thanks for taking that feedback in stride. I like your example of vim, and how Bram drew from a wealth of experience - not just in software - to inform his decisions for vim. I'd love to see you discuss that example in the original article, and maybe even some more from the list. THAT would be a compelling article.