Thursday, September 13, 2012

United States Patent: 8254902

Is that a threat as in “We should turn off this fellow’s cell phone because he is texting about his autobiographical screenplay while driving,” or as in “Stop him—he is organizing a protest march against the politically powerful?”

Moreover, in certain situations, the communications capability that the wireless device accords to its user may be what poses the threat.

United States Patent: 8254902

Wednesday, September 5, 2012

SQL vs. NoSQL | Linux Journal

I am well acquainted with the benefits of non-SQL approaches to data management. And I honor those who speak responsibly about the differences between relational and non-relational approaches, including one of my current clients, a vendor of a highly scalable non-SQL DBMS.

I’ve also noticed some irresponsible prattle on this topic, as has the author of this excellent article in Linux Journal.

This scaling myth is perpetuated and given credence every time popular Web sites announce that such-and-such RDBMS doesn't meet their needs, and so they are moving to NoSQL database X. The opinion of some in the RDBMS world is that many of these moves are not so much because the database they were using is deficient in some fundamental way, but because it was being used in a way for which it wasn't designed. To make an analogy, it's like people using flat-head screwdrivers to tighten Phillips-head screws, because it worked well enough to get the job done, but now they've discovered it is better to tighten Phillips screws with an actual Phillips screwdriver, and isn't it wonderful, and we should throw away all flat-head screwdrivers, because their time is past, and Phillips is the future.

One recent SQL-to-NoSQL move involved Digg.com moving from MySQL to Cassandra. As part of the move, Digg folks blogged about how they were using MySQL and why it didn't meet their needs. Others were skeptical. Dennis Forbes, in a series of posts on his site (see Resources), questioned whether Digg needed to use a NoSQL solution like Cassandra at all. His claims centered on what he considered very poor database usage on the part of Digg combined with inadequate hardware. In his mind, if Digg had just designed its database properly or switched to using SSDs in its servers, it would have had no problems. His best quote is this:“The way that many are using NoSQL is like discovering the buggy whip at the beginning of the automotive era.” Ouch.

SQL vs. NoSQL | Linux Journal

With Rise of Gene Sequencing, Ethical Puzzles - NYTimes.com

Reminds me of the “Fruit of the Poisonous Tree” metaphor from criminal law—which dictates that certain evidence and all evidence that flows from it—must be ignored if it was collected illegitimately.   That case and this one shed some light a human aspect of information quality: That our civic institutions sometimes demand (legitimately, in my opinion) that high-quality data be ignored.

Dr. Arul Chinnaiyan stared at a printout of gene sequences from a man with cancer, a subject in one of his studies. There, along with the man’s cancer genes, was something unexpected — genes of the virus that causes AIDS.

It could have been a sign that the man was infected with H.I.V.; the only way to tell was further testing. But Dr. Chinnaiyan, who leads the Center for Translational Pathology at the University of Michigan, was not able to suggest that to the patient, who had donated his cells on the condition that he remain anonymous.

With Rise of Gene Sequencing, Ethical Puzzles - NYTimes.com

Friday, August 24, 2012

Day4 - How we screwed (almost) the whole Apple community (updated)

A chilling—not terribly surprising—story about using the internet echo chamber against itself.

With each step further away from the source ,the perception that this would be true, increased. On Reddit, where the original entry was made we saw it as a 0 mode, the image was posted, nothing more or less. Newspapers and blogs who drew attention to the whole thing (Yahoo, Macworld, Wired) took it with a grain of salt, so the truth factor goes down a bit. The commentators to the articles however took it almost as 100% truth, raising the truth factor bar. The commentators / readers who tok it further in their own social media (Twitter, G +, Facebook) defined it as the truth, all doubt is gone. In what segment do you pick up your information, and which one affects people the most?

Day4 - How we screwed (almost) the whole Apple community (updated)

Language Log » One little adjective

More on data quality in the public sphere. A shame here is that even those who have the rhetorical wherewithal to create nuanced criticism can opt for sound-bite-ready snarkiness instead. Our friends at language log illuminate and clarify once again:

But in the meantime, a warning to candidates for elective office: watch every word, every little attributive adjective. You may not have meant it the way it sounds; they may not even believe you meant it; but if you utter even a two-word phrase that sounds outrageous, that'll be enough rope for them to hang you with. They are playing linguistic Gotcha, and the game is deadly serious, and losers don't get elected. Be careful out there. Get your adjectives checked out by a linguist up front. And stay away from TV studios if you aren't a master of on-the-fly self-editing.

Language Log » One little adjective

Botched Restoration of Ecce Homo Fresco Shocks Spain - NYTimes.com

Yes, data quality is everyone’s responsibility, but that obviate the need for professionals.

A case of suspected vandalism in a church in a northeastern village in Spain has turned out to be probably the worst art restoration project of all time.

An elderly woman stepped forward this week to claim responsibility for disfiguring a century-old “ecce homo” fresco of Jesus crowned with thorns, in Santuario de la Misericordia, a Roman Catholic church in Borja, near the city of Zaragoza.

Botched Restoration of Ecce Homo Fresco Shocks Spain - NYTimes.com

Friday, April 6, 2012

A Mistake Too Amusing To Let Stand

Imagine my glee when I encountered the first paragraph of a story in the dead-tree version of the New York Review of Books:

Tony Judt had a thing about railway trains.  We even know from his last book, a brilliant compilation of his ideas on history and politics, distilled just before his untimely death from a series of conversations with Timothy Snyder, that he had wanted to write a history of trains, entitled Locomotion.

I decided then and there to write a blog post, which is not what you are reading now because my plans changed when I sought out the on-line version of the same article and found this:

Tony Judt had a thing about railway trains. We even know from his last book, a brilliant compilation of his ideas on history and politics, distilled from a series of conversations with Timothy Snyder just before his untimely death, that he had wanted to write a history of trains, entitled Locomotion.

Okay, that’s a bit better, now we know that talking to Timothy Snyder was not fatal.  But who died?  The dead-tree draft at least made it clear that Tony Judt was dead.  The on-line version suggests that Timothy Snyder is the dead guy:

“…a series of conversations with Timothy Snyder just before his untimely death…”

The writer (Ian Buruma) seems unable to get out of his own way.  So, the snarky blog entry I had intended to write—about an apparently fatal conversation with Timothy Snyder—has expanded. 

The expanded scope includes:

  • Data quality for narrative data.
  • Clarity: A rule of thumb for amateur writers.
  • Obviousness in examples—expect stupid rebuttals.
  • The ethics of changing already-published material.

I’ll cover these topics in upcoming posts.  I’ll add the links to this post as they become available.  Stay tuned.