Pages here pile up beside each other in what we call the Lineup, federated wiki's most distinguishing feature. Here I recall antecedents and then get to discussing how I remember with some efficiency.
We thought that a Fortran program's structure and expression could be captured on the screen in a way that it only appeared in the mind of the programmer.
Mind ⇒ Screen ⇒ Mind.
See the lineup here, running vertically down the page, with each subroutine displayed immediately below the call and a synopsis provided for each.
I collaborated with Randal Hansen on this. Notice that he found the keystroke ESC too magical and proposed some additional affordance to remove unwanted screens.
.
On a personal level, what I liked most about reading wiki is that this work from a decade ago was still close at hand and I can show you how I got to it. No such luck with any other computer based information retrieval system I've ever used.
> it might make sense to people in this context, ward, to me for sure, for you to describe the mental process, from initial intention formation to screen, of how the work was still close at hand and show how you got to it. matrix 
I've expressed an interest in Mind ⇒ Screen ⇒ Mind. Myst was creative hypertext born of two brothers and realized in HyperCard. One might preserve Myst by getting some old binaries together and a sim powerful enough to bring it back to life. That would be recreating the old screen on a new screen.
Screen ⇒ Screen.
As a programmer with some familiarity with HyperCard, I wonder, what were they thinking and how did they use computers to help them think before Myst was a thing? They have described what they did often enough that I have a pretty good idea.
Mind ⇒ Mind.
But what would be possible with today's computing power to create an experience that duplicates their creative genius? What would that experience leave in the minds of the curious that simply playing the game does not?
Mind ⇒ Screen ⇒ Mind.
When federated wiki was young I wanted to experience using it to describe complex ideas like those involved in creative thought. I have vivid memories of many programs I have written especially when bringing them to life taught me things that I continue to use to this day. Thus I set out to write a page about every program I've ever written that comes to mind repeatedly. I might ask myself, what do I remember that brought that experience to mind? Have I written that page yet? If not, write it now.
.
Mike suggested that wiki is hard to read. I could have asked what folks find hard. Instead I though, what quirky things do I love about wiki and how is it that I know to appreciate them? matrix
Randal came to mind. I liked the code we wrote together and surely must have written about that. I knew the program that we studied. It was written when I was in college so click-click I'm looking at that list. I didn't see it but I did see Imlac mentioned and it ran on Imlac so click-click I'm there. The page mentioned several restorations so click-click again and Randal's code is running. Click-click some more and I am back in college coding that thing. Amazing.
I had documented many programs before I realized that where I wrote them was as strong in my memory as what they did or what I learned. Those places all had names so that became the after-the-fact index to my life of programming.
Had I not had that I might have searched around on code.fed.wiki.org for a while. I might have had to search on sites.fed.wiki.org to remember even that place. I scatter things all over just to test my ability to find things.