( ? , qUeStIoNMaRk )

I’ve been toying around the idea of using a more agile publishing platform; i.e. a (digital) place without all the bells and whistles and the “sense of ceremony” of this blog thing. Well, the sense of ceremony is supposed to belong to a distant universe very far from the blogosphere but, you know, that draft-feature in WordPress has a terrible effects on my procrastinating-self.

So I started an alternative brain dump somewhere else, the place is http://mrfabbri.posterous.com.

The future of television is digital terrestrial.

On digital terrestrial you see a whole lot of nothing.

The future of television is (seeing) a whole lot of nothing.

(with apologies to the original “Trains whistle/Socrates whistles/Socrate is a train” thing).

In other news…

Microsoft releases its first iPhone app: “the application allows users to browse high-resolution images, according to information provided by Microsoft. The application is optimized for use over 3G and Wi-Fi networks“. (Which in other words means it is not optimized for any low bandwidth connection)

I am holding an iPhone in my hands.

UPDATE: I also mistook the past tense of freeze, which by no means is freezed, brrr…

…I didn’t.

Now let’s take some time to ponder on the question at the end of the video.

Notwithstanding Google Reader subscriptions getting fatter and fatter and Facebook Live Feed reaching flood level, I had to try, I couldn’t help myself but to begin twittering.

If you can read this, thank your sysadmin

Today is System Administrator Appreciation Day. From (the wikipedia entry on sysadmin Dasy) :

System Administrator Appreciation Day, also known as Sysadmin Day, SysAdminDay or SAAD, was created by Ted Kekatos, a system administrator in Chicago. Kekatos was inspired to create the special day by a Hewlett-Packard magazine advertisement in which a system administrator is presented with flowers and fruit-baskets by grateful co-workers as thanks for installing new printers.[1] The holiday exists to show appreciation for the work of sysadmins and other IT workers. It is celebrated on the last Friday in July. The first System Administrator Appreciation Day was celebrated on July 28, 2000.

As a side note I may suggest you take a while to read this beautiful and involving novel by Cory Doctorow “When Sysadmins Ruled the Earth”.

Happy Sysadmin Day!

Here comes a video demoing SeekTube functionality.

Clifford Stool’s talk at TED is an absolutely awesome and brilliant learning experience. This talk reveals all the energy, the passion, the hope that lie in scientific inquiry and in an agile mind. As a side effect this should also make you wonder at the propulsive push to the development of a society/country this sort of attitude brings…

“The first time you do something it’s science, the second time it’s engineering, the third time it’s technology, it’s just being a technician. I’m a scientist: Once I do something, I want do something more.”

“I think if you want to really know what the future is gonna be… If you really want to know what society is gonna be in twenty years, ask a kindergarten teacher. In fact don’t just ask any kindergarten teacher, ask an experienced one.
[…]
“I think locally and I act locally, I feel the best way I can help out anything is to help out very very locally… I teach eight-grade science four days a week… I said to my science students: we are going to do seriuos experiments, none of this “open the chapter seven and do all the problems sets”, we are going to be doing genuine physics.

Joel wrote, as usual, a thoughtful and witty article on the web, standards, interoperability and the upcoming mother of all flame wars; this is a must-read for everyone concerned with web-related software development (web designers, web programmers, information architects, marketeers…) .

As usual, the idealists are 100% right in principle and, as usual, the pragmatists are right in practice. The flames will continue for years.

Joel goes into a lengthy explanation, driven by an extra-terrestrial catchy case study, of what are the possible “cardinalities” of “market standards” (One-to-One - all is fine and simple, One-to-Many - yet fine, Sequence-to-Many - a story of pain and backward compatibility, Many-to-Many - you know, PurePain ™), why a standard without a reference implementation it’s not that standard, and why in the long run being conservative in what you do, and being liberal in what you accept from the others potentially ends in deployment issues kicking your conservative yet liberal butt. In the meanwhile you get also acquainted with some real-world compatibility issues between rabbis from different ultra-orthodox communities:

If you’ve ever visited the ultra-orthodox Jewish communities of Jerusalem, all of whom agree in complete and utter adherence to every iota of Jewish law, you will discover that despite general agreement on what constitutes kosher food, that you will not find a rabbi from one ultra-orthodox community who is willing to eat at the home of a rabbi from a different ultra-orthodox community. And the web designers are discovering what the Jews of Mea Shearim have known for decades: just because you all agree to follow one book doesn’t ensure compatibility[…]

As a very brief personal memorandum: Real Standards must have Real Reference Implementations (because “reality siphons off excess complexity“¹) and although Postel’s Robustness Principle is (imho) still much valuable for the wide spread of the internet/web it has been able to sustain so far, it should be carefully balanced - “in medium stat virtus” - with having very, very strict standards and “components” positively obnoxious about pointing them all out to you; maybe we (as developers/engineers) should resort to some sort of “carrot and stick” principle.

NOTE ¹: The full citation from David H. Gelernter’s Mirror Worlds (a wonderful and fascinating book narrating a vision of computing and information of extraordinary elegance - that is by other words a good combination of simplicity and power) is:

“Information structures are, potentially, the most complicated structures known to man. Precisely because software is so easy to build, complexity is a deadly software killer.
The same problem exists for hardware machines, but it lacks comparable significance. Physical reality is the overflow valve that siphons off excess complexity before the whole system blows.[…]”.