HackerTube 中文?
Representation, intuition and feedback →

After an edit, how can you see what actually changed?

A green test, a live picture and a replayable history all count as feedback. Follow one edit and ask which consequences become visible and which still need reflection.

Questions in this reading · 6
  1. How quickly can a programmer see a mistake?
  2. What if feedback arrived with the edit?
  3. Can creators see the effect of an edit?
  4. What can you stop imagining once an edit is visible?
  5. How can an environment make time visible?
  6. Must we choose between reflection and instant feedback?

How quickly can a programmer see a mistake?

Running tests on every file change shortens one feedback loop. Showing the changing behavior beside the edit shortens another. The signals tell the programmer different things.

Compare original passages and timestamps · 2
each time something changes in the directory it reruns the command
A Tour of the Acme Editor · ▶ 20:20–20:39
if you make a change or you make a decision you need to see the effect of that immediately
Bret Victor - Inventing on Principle · ▶ 2:06–2:18

What if feedback arrived with the edit?

One talk traces a search for shorter feedback loops. The other shows what creators can discover when the result is continuously visible.

Compare original passages and timestamps · 2
What if we shortened the feedback loop to effectively nothing
In Search of Tomorrow · ▶ 4:08–4:11
creators need an immediate connection to what they create
Bret Victor - Inventing on Principle · ▶ 2:01–2:08

Can creators see the effect of an edit?

A notation tool and a programming environment both make an edit visible. Look for the precise gap each closes between an action and the result its author can inspect.

Compare original passages and timestamps · 2
...by making the arrow a subtle shade of blue? Do you know how hard that is to see?
Music Software & Bad Interface Design: Avid’s Sibelius · ▶ 19:04–19:10
you need to see the effect of that immediately
Bret Victor - Inventing on Principle · ▶ 2:08–2:16

What can you stop imagining once an edit is visible?

Two programming environments and a notation editor let their users inspect the effect of an edit. Feedback reduces mental simulation without guaranteeing conceptual understanding.

Compare original passages and timestamps · 3
if you make a change or you make a decision you need to see the effect of that immediately
Bret Victor - Inventing on Principle · ▶ 2:08–2:16
So I could literally watch the data flow through my program.
In Search of Tomorrow · ▶ 4:56–5:01
...by making the arrow a subtle shade of blue? Do you know how hard that is to see?
Music Software & Bad Interface Design: Avid’s Sibelius · ▶ 19:04–19:10

How can an environment make time visible?

One demonstration makes behavior visible while editing on a screen. Another brings that feedback into a physical workspace. Compare what the maker can inspect in each setting.

Compare original passages and timestamps · 2
immediately you have to map time to space
Bret Victor - Inventing on Principle · ▶ 13:38–13:47
look across a range of time at once
Bret Victor - Seeing Spaces · ▶ 8:15–8:21

Must we choose between reflection and instant feedback?

Thinking away from the keyboard helps frame the problem. A responsive medium helps inspect an idea once expressed. The two techniques address different moments in the work.

Compare original passages and timestamps · 2
you're going to try stuff and go back
Hammock Driven Development - Rich Hickey · ▶ 37:44–37:51
creators need an immediate connection to what they create
Bret Victor - Inventing on Principle · ▶ 2:01–2:08

Try it on your own example

Take a recent edit. Which intermediate state would disappear if you saw only the final frame?