Gregory's Serverall of the aforementioned are far from rigorous explorations of solutions. treat the above with a grain of salt.
|
2 comments
 a document which provides implementation details or a self-documenting implementation is more valuable than an implementation |
the idea I'm getting at has less to do with any specific implementation and more about the lens through which implementation of software with a target host OS is perceived.
imagining your implementation not as a single piece of software but as a set of constraints and implementation details... as an agnostic set of instructions that can be easily replicated under arbitrary conditions.
the blueprints to a shovel and not a shovel
the rules to a game that the world can play, not a game