model recovery
Great term of art for e.g. scraping.
model recovery
Great term of art for e.g. scraping.
A major purpose of this style is Malleable Software, or software that is more supportive of change, reusability, and enhancement.
Is this the first occurrence of this term?
One of the problems with building a jargon is that terms are vulnerable to losing their meaning, in a process of semantic diffusion - to use yet another potential addition to our jargon. Semantic diffusion occurs when you have a word that is coined by a person or group, often with a pretty good definition, but then gets spread through the wider community in a way that weakens that definition.
I like to call it inverse vandalism (when vandalism is destroying things just because one can, then inverse vandalism is making things because one can).
what I've called the barefoot developer
what I call "SQL-by-mouse"
Comparing pancakes to file management is an apples to oranges comparison.
From this point onwards, I'm going to insist that anything that uses the phrase "[...] apples and oranges" omit it in lieu of the phrase "like comparing filesystems and pancakes".
An ActivePaper is, by defini-tion, a package combining the code, data, and documentationthat describe together a computational scientific study.
There is a good chance that you have never heard ofsoftware collapse before, for the simple reason that it’s aterm I have made up myself two years ago in a blog post.
conceptual parsimony
Node severely complicates and confuses things, but node alone is not javascript.
"'JS' does not mean 'Node'"
The atomic unit of developer productivity ought then to be one iteration of the inner loop. The appropriate unit is not code quantity, but iteration frequency. We might call this unit of quantity developer hertz.
So, I’m going to coin a term, Personal Digital Habitat
quietly interesting
the guide shall be written in such a way that all we have to do is produce the guide itself and then a computer can do the heavy lifting—where we might otherwise expect a separate, possibly GUI-driven, "app" to be created for the end user to interact with, we accomplish the same effect by making the guide very detailed—in part also an attempt to evoke the style and quality of old equipment operation and repair manuals that used to be available, when such manuals could be expected to include e.g. full schematics. If done correctly, this should be sufficient for the guide itself to be interpretable by a machine.
"comprehensive codebook"?
line in the sand between the old and new "smart" phone worlds
I like this distinction—"new world" smartphones vs "old world" smartphones.
the frothy web
public type registry
Any known previous occurrences to this phrase? It's used today in the Solid Project.
There used to be an internet middle class, of non-commercial users whowere not overtly technical, but were still able to self-publish.
This is probably the least flawed claim in the entire piece.