The article is badly written. For example, > The problem with coding, he says, is that you can’t see the results of your work until after you’re done. In that

The article is badly written. For example, > The problem with coding, he says, is that you can’t see the results of your work until after you’re done. In that sense, programming is unlike almost every other craft. “When a chef adds an ingredient, he can smell it, he can taste it,” Granger says. “When an artist makes a stroke on a canvas, he can see it. But programming isn’t that way.” The rest of us would say we just run our unit tests in a couple of seconds and call it a day. At least, if you didn't watch the video. The video shows a potentially useful tool (on Clojure no less). It's more about watching the propagation of values through code, than it is about "feedback" per se.