(home)
📝
relationships between high level code things: modularity,
composability, abstraction, etc
relationships between high level code things: modularity,
composability, abstraction, etc
- type: note
-
-
- The opposite of abstract is concrete
-
See
-
Abstraction: Not What You Think It Is
In programming language theory and formal methods, there are several definitions of "abstraction" in different contexts, but they are all quite similar: abstractions are mappings between a complex concrete world and a simple idealized one.
-
-
I think
🎞️ Constraints Liberate, Liberties Constrain
has the best simple example of abstraction I've seen
- Working for a poetry publisher
-
Had a program
Doc -> List PrinterInstruction-
Requirements changed, now need to
- Manipulate documents, eg put them side-by-side
- Target a new printer
-
Introduced an
IRabstraction-
Doc -> IR -
IR -> List PrinterOneInstruction -
IR -> List PrinterTwoInstruction
-
-
Requirements changed, now need to
-
-
Opposite is emergent effects
-
This is described here:
🖊️ On compositionality
- Read the whole thing, it's really good
-
This is described here:
🖊️ On compositionality
- On the distionction between compositionality and composability, see this StackOverflow post
-
Opposite is emergent effects
-
- Opposite is openness
- lots of back and forth on what encapsulation really is here: wiki.c2.com/?EncapsulationIsNotInformationHiding
-
implementation
-
wikipedia non-exact match
- a very general article: en.wikipedia.org/wiki/Implementation
- a stub: en.wikipedia.org/wiki/Software_implementation
- Related to specification and interface
-
wikipedia non-exact match
-
- Related to implementation
-
specialization
and
generalization
-
specialization
- no Wikipedia article surprisingly, though there is a disambiguation page: en.wikipedia.org/wiki/Specialization
- en.wikipedia.org/wiki/Hyponymy_and_hypernymy
-
-
- Related to implementation