HackerAfter 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 · 12
- How quickly can a programmer see a mistake?
- What if feedback arrived with the edit?
- Can creators see the effect of an edit?
- What can you stop imagining once an edit is visible?
- How can an environment make time visible?
- Must we choose between reflection and instant feedback?
- From a single edit to a usable prototype
- Does a local replay actually start from the same frame?
- Did the avatar send the right expression in time?
- Why handle a component if you can order it the same day?
- After seeing a failure, how soon can you try again?
- Why is the page still stuck after using asynchronous callbacks?
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 commandif you make a change or you make a decision you need to see the effect of that immediatelyWhat 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 nothingcreators need an immediate connection to what they createCan 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?you need to see the effect of that immediatelyWhat 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 immediatelySo I could literally watch the
data flow through my program....by making the arrow a subtle shade of blue? Do you know how hard that is to see?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 spacelook across a range of time at onceMust 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 backcreators need an immediate connection to what they createFrom a single edit to a usable prototype
The Cursor team wants a suggestion to arrive before the next edit. Levels works at a different granularity: as a sole operator he can shorten the interval between writing and shipping. Kay’s Alto made a future machine’s interactions usable early, on an expensive stand-in. These loops test different predictions: the next edit, demand for a shipped feature, or the viability of an interaction model. Fast completion cannot answer the third question.
Passages and timestamps · 3
predicting what the user’s going to do next in their editing of existing codebeing alone by myself on my laptop, in my underwear in a hotel room or something, I can ship very fastit was there to simulate this laptop of the futureDoes a local replay actually start from the same frame?
Sanderson repeatedly runs a small part of a Manim animation to tune it. Pasting the same code again would run it on a scene already changed by the first pass. His replay restores the state at the section’s start. A cheap check for a live preview is to replay twice without editing. If the images already differ, the preview cannot yet isolate the effect of the next edit.
Passages and timestamps · 1
It has to revert to the state that the scene had at the start.Did the avatar send the right expression in time?
Zuckerberg explains how scans across expressions build an avatar that can then be driven by an encoded signal during a call. Carmack supplies another acceptance condition: subtle reactions must arrive in time for two people to feel together. Put a raised eyebrow, its display and the partner’s response on one timeline. A still frame checks the reconstructed expression. A back-and-forth exchange tests delay. A more convincing frame leaves that second question open.
Passages and timestamps · 4
scanned ourselves in a lot of different expressionssend an encoded version of what you're supposed to look like over the wirethe super low latency responsivenessjust occupying the same field of viewWhy handle a component if you can order it the same day?
Kay’s flight example asks how soon a failed experiment can be tried again. Shenzhen’s component markets add the waiting before a trial begins. One entrepreneur describes some locally ordered parts arriving that afternoon or the next day; another explains why photographs and specification sheets are insufficient for choosing a switch: feel, size and mounting details need direct inspection. Nearby parts reduce waiting and expose a poor choice earlier; a suitable model can then be purchased in quantity in the same market. Separate these steps to distinguish faster procurement from earlier testing of a product assumption. The documentary’s later discussion of rents and urban villages adds a dependency: these conditions require suppliers, workspace and local experience together. A faster tool for an individual team cannot simply reproduce that network.
Passages and timestamps · 2
we can order in the morning and then we get it in the afternoonyou want to know how it feelsAfter seeing a failure, how soon can you try again?
An immediate display shortens only part of a feedback loop. Kay’s account of human-powered flight contains a slower step: after a prototype crashes, will repair consume months? In his telling, MacCready first sought a design that could fail repeatedly in a day and be repaired in minutes, making more informative trials possible. Bring that question back to programming tools. Alongside time-to-result, measure time-to-next-experiment. Reversible edits and recoverable test environments may remove a bottleneck before faster screen updates do. This is a design question drawn from the case, not a law Kay established for every research process.
Passages and timestamps · 2
we need to be able to do 12 crashes a dayyou could fix it in a few minutesWhy is the page still stuck after using asynchronous callbacks?
Draw “work has been queued” and “the user has seen the result” as two separate events. In Roberts’s sequence of timers, later callbacks still wait behind earlier work, so a one-second delay is an earliest-execution condition, not a promise to execute at one second. His scrolling example adds another failure mode: events enqueue quickly while slow work accumulates in the queue. Use that model to trace a feedback tool through input, queueing, execution and rendering. Replacing a synchronous loop with callbacks does not automatically shorten the whole path. The simplified rendering queue in his animation exposes waiting points; it is not a complete specification of every browser’s scheduler.
Passages and timestamps · 2
it's a minimum time to executionyou're flooding the queue with queued events.Try it on your own example
Take a recent edit. Which intermediate state would disappear if you saw only the final frame?