nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpquvfvlddmhuh4hu4teupjs2lkdn8x3htrrw7jlwzuv0ushumkwnhq6n66f2 While I think effect is somewhat captured by the second point, I think it is distinct enough to warrant it's own bullet. So yeah I'll add that one.

Related to that is domain knowledge of a program. The absolute most basic step to understanding a program is knowledge of what the program does at the user level (its inputs and outputs) that the user experiences. That particular thing though is likely less relevant to this project because I am not sure what tool I would write to help with that.

Reply to this note

Please Login to reply.

Discussion

nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpquvfvlddmhuh4hu4teupjs2lkdn8x3htrrw7jlwzuv0ushumkwnhq6n66f2 unrelated to any of this, I think I have the central theme for this tool: locality. The premise is simple and obvious: things which can be brought together can be easily understood. Things that remain disparate are hard to understand.

In a way, the entire act of forming a mental model is simply an exercise in increasing locality of information.

So if you can have a tool in an IDE that can "rope in" the parts of a system you care about tightly together, visually and temporarily, I think that could quickly go a long way to building a mental model.