This paper presents concepts for building interactive applications, from philosophical to concrete implementation. I read it several times, and will read it aga

This paper presents concepts for building interactive applications, from philosophical to concrete implementation. I read it several times, and will read it again, because there are some unique insights that helped me understand my work in a new way. One idea I liked was viewing the user/developer as an artisan. He emphasizes the importance of tools that provide immediate feedback, to give the illusion that the user is working directly on the object he is building; utilize hand-eye-brain coordiantion (visual builders, WYSIWYG editor..) This reminded me of developing with file watch/build/live-reload, where a live application is evolving as I write the code. As he puts it: "in-place transformation of the working material: a single always-working application being gradually transformed from its initial to its final form" That's agile. Later in the paper, he describes an application model with components and "unidirectional flow". I don't know when this was written, but it's interesting how this paradigm is gaining wide acceptance these days.