System Design

#
>

Principles

→
#
>

Minimal moving parts

→
#
>

Minimal connections

→
#
>

No domain specific knowledge required, easy to pick up system management

→
#
>

Under-engineered, leaving flexibility for future technology improvements and unforeseen issues.

→
#
>

A nice alternative name for this idea is Functional Design

→
#
>

Abstracted

→
#
>

Technical components have direct representations in a clear, abstract mental framework.
This means that the system can be described accurately without reference to the technical components.

→
#
>

The levels of a system

→
#
>

The top layer (the interface)

→
#
>

This is the layer that is visible to the “user” of the system

→
#
>

The bottom layer (the backend)

→
#
>
→
#
>

Andy Matuschak notes

→
#
>

Effective system design requires insights drawn from serious contexts of use
https://notes.andymatuschak.org/z3H98n8DGZmu8XArqHZVsckyWvbTe8wK4kAt2

→
#
>

Great tool-makers are often not great tool-users, and vice-versa
https://notes.andymatuschak.org/zagVn3aaVDFhU4JhGCntgs88oHMJSpzu7ar

→