Building the smallest version that can teach you something
A practical way to separate an experiment from a disguised production system.
A useful first version does not prove that the final product will work. It reduces one important uncertainty with the least machinery possible.
Start with the question
Before choosing a framework, write down the decision the experiment needs to inform. If the result cannot change what you build next, the experiment is only a demonstration.
Small systems are valuable because their failures are legible. You can see what you assumed, what the user did, and where those two stories diverged.