I now use Are.na as a Memory Palace, separating my channels into rooms. For example, I have a channel that I call the Computation Room. It’s pretty generic and includes any type of block that relates to computation.
If I notice a pattern in the computation room I create a more specific channel in that room. I think of that more specific topic as an object within the room.
Then there are the adjacent topics that I often find even more exciting to focus on. For those, I choose a name that corresponds with the nature of a room and also its size. For example I have a channel called the Visual Computing Observatory. In my head I am imagining an actual observatory where I am looking and observing and studying a given topic.
Engineers seem to have a clear, if usually implicit, model of the process of design. It is usually an orderly model of an orderly process as the engineer conceives it.
The notion that the design process should be modeled as a systematic step-by-step process seems to have first developed in the German mechanical engineering community.
Herbert Simon independently argues for design as a search process in The Sciences of the Artificial. He was motivated to lay out a strictly rational model of design precisely because such a model was a necessary precursor to automating design. His model remains influential even if today we recognize the "wicked problem" of original design as one of the least promising candidates for AI.
In software engineering, Winston Royce independently introduced a seven-step Waterfall Model to bring order to the process. In fact, Royce introduced his waterfall as a straw man that he then argued against, but many people have cited and followed the straw man rather than his more sophisticated models. Even if ironically, Royce's seven-step model must be considered one of the foundational statements of the Rational Model of Design.