Category Archives: blurb

Links (& blurbs about them)

I drink it up. Two different ways.

I’ve found two nifty “I drink your milkshake” t-shirts. This one is the best:

I drink your milkshake!

And this one deserves an honorable mention.

While you’re at it, buying this shirt will go towards saving the historic Hill Valley Clocktower.

Plus, this is a particularly nice execution of angels having the phone box.

Th’ ol’ Facey-Bee

Attention: Henceforth Facebook shall be referred to by its new and proper name, “Facey-Bee.” Alternatively, “th’ ol’ Facey-Bee” will also be accepted. Thanks for your attention to this urgent matter.

Another browser-side Model-View-Controller analogy

Coding Horror presents another way to think about the browser side of web apps as underlyingly MVC in Understanding Model-View-Controller. It’s interesting, but I still prefer my analogy for primarily AJAX web apps; when the data comes in primarily through XMLHTTPRequest, it doesn’t make much sense to think of anything but the JavaScript that handles XMLHTTPRequest responses as the model.

Memristor: a paradigm shift?

R. Stanley Williams at Hewlett Packard, in an article published in Nature, appears to have invented the memristor. And according to Professor Leon Chua of UC Berkeley, this represents more than just a nifty new chip component; it’s a total paradigm shift:

Electronic theorists have been using the wrong pair of variables all these years — voltage and charge. The missing part of electronic theory was that the fundamental pair of variables is flux and charge. The situation is analogous to what is called Aristotle’s Law of Motion, which was wrong, because he said that force must be proportional to velocity. That misled people for 2000 years until Newton came along and pointed out that Aristotle was using the wrong variables.

Chua, in the Information Week article, goes on to explain that this will have major ramifications for neural-net processing and power consumption. If this is all for real, it means we’ll someday be looking back on computing equipment produced in the last forty years as not just slow, oversized and outdated, but hopelessly primitive because it was designed based on faulty assumptions and is missing whole categories of useful functionality. How exciting.

Empirical debugging

Steve Hazel‘s Debugging Science puts the science back in computer science by pointing out the deep similarities between the empirical/scientific method and the best debugging practices.

From this point of view, the open-source call to arms “with enough eyes, every bug is shallow” even turns out to be a similar kind of parallel “processing” as modern academia’s “multiple camps in support of divergent theories.”