What Does the Computer Want?

Here I quote my own introduction to the "learning from incidents" folk with whom I will share a panel.

True confession: I'm a slow reader but a fast programmer. I was careful in graduate school to only take classes that included a programming project. I might be way behind at the midterm but I would catch up as soon as the class started working on their projects. Even graduate students would approach programming by writing the statements that told the computer what they wanted it to do. Instead I wrote statements that told me what the computer wanted to do. It seems indirect. But batch turnaround was two hours and I learned something interesting every turnaround.

My skills predate the wide spread use of REPL because my work predates my access to interactive timesharing. See Creativity Before and After Agile

Here I defend my emerging vision of programming at scale. See Are We a Model or a Document?