Friday, August 31, 2012

"The Coming Civil War over General-purpose Computing" - Cory Doctorow



Alt. Video Src.: http://youtu.be/gbYXBJOFgeI

" Who governs digital trust?

Doctorow framed the question this way: "Computers are everywhere. They
are now something we put our whole bodies into---airplanes, cars---and
something we put into our bodies---pacemakers, cochlear implants. They
HAVE to be trustworthy."

Sometimes humans are not so trustworthy, and programs may override
you: "I can't let you do that, Dave." (Reference to the
self-protective insane computer Hal in Kubrick's film "2001." That
time the human was more trustworthy than the computer.) Who decides
who can override whom?

The core issues for Doctorow come down to Human Rights versus Property
Rights, Lockdown versus Certainty, and Owners versus mere Users. "

....

Hugh Herr at TEDMED 2010



Alt. Video Src.: http://youtu.be/8AoRmlAZVTs

MIT's Hugh Herr demonstrates the latest generation of robotics

Monday, March 12, 2012

A Better Way To Program

" Written by Alex Armstrong
Saturday, 10 March 2012 11:04

This video will change the way you think about programming. The argument is clear and impressive - it suggest that we really are building programs with one hand tied behind our backs. After you have watched the video you will want the tools demonstrated.

We often focus on programming languages and think that we need a better language to program better. Bret Victor gave a talk that demonstrated that this is probably only a tiny part of the problem. The key is probably interactivity. Don't wait for a compile to complete to see what effect your code has on things - if you can see it in real time then programming becomes much easier. Currently we are programming with one arm tied behind our backs because the tools that we use separate us from what we write and what happens.

Interactivity makes code understandable.
Moving on, the next idea is that instead of reading code and understanding it, seeing what the code does is understanding it. Programmers can only understand their code by pretending to be computers and running it in their heads. As this video shows, this is increadibly inefficient and, as we generally have a computer in front of us, why not use it to help us understand the code?.... " - continued: http://goo.gl/o9w8e

....



....

Alt. Video Src.: http://vimeo.com/36579366

- - continued: http://goo.gl/o9w8e