re code literature plan

I think I can distill something interesting out of those musings on software architecture from the previous post:
Let's build software that is more forthcoming about its methods in the interface.
Definition of terms:
An application uses methods, or algorithms, to do what it does, when we ask it to do something. Runtime activity can be logged in the general form "the program is running this method ..." Someone could "ask" and the software could explain something about how the method works. This is probably just two examples of ways a program can report on its methods.
The interface is a graphic which shows what the program does. It also commonly does report, to some extent, on what the program is doing. My proposal: build interfaces that show a lot about 1) how the program does a thing (beyond what that thing is) 2) what the program is doing 3) what the program has done in the past.
This doesn't replace what I described earlier, rather, it's another separate (related) practice.