Week #2 of this new project to highlight interesting tidbits from the previous seven days. Well, things that were interesting to me that I hope will be interesting to DLTJ readers. Time will tell.

Technical Debt: A Perspective for Managers

What is Technical Debt? It’s all “those internal things that you choose not to do now, but which will impede future development if left undone” [Ward Cunningham]. On the surface the application looks to be of high quality and in good condition, but these problems are hidden underneath. QA may even tell you that the application has quality and few defects, but there is still debt. If this debt isn’t managed and reduced, the cost of writing/maintaining the code will eventually outweigh its value to customers.

Technical Debt is like a credit card that charges a high interest rate, just leaving the team with an outstanding balance cost. In this case, the costs are represented by time and effort needed to work around the problems. The longer the team takes to pay off the debt, the more interest is accumulated (in the form of additional workarounds) and the higher the costs for the business.

This definition of the amorphous stuff that gets in the way of moving faster really resonates with me.

A Case of Taking QR Codes to the Park

[Fort Smith Park Superintendent Bill Black] sat through a few conference sessions held by the Arkansas Parks and Tourism Department about information technology, where he heard about QR (or Quick Response) codes—which are two-dimensional bar codes that can be used in a variety of ways. A company can choose from any number of sites that will generate a QR code for free and put that code almost anywhere—on a website, a postcard, or even a T-shirt. Then smartphone users use the camera on their phones to scan the bar code—some phones have the scanning technology built in, but older iPhones and the like will have to download a free app—and are instantly taken to whatever content is linked to the bar code.

“On the drive home I got thinking about how it might work for interpretation purposes,” Black says, and he began to consider how this technology might be deployed to provide information to park visitors.

Econtent Magazine has this brief use case for QR Codes as a way to link to more information in a national park. Usage of QR Codes seem to be creeping up, helped in no small part by efforts at Google in its Favorite Places and URL Shortner services. They aren’t exactly common yet, but this is a place where libraries might get ahead of the game. There have been several experiments with QR Codes in OPACs and other services, for instance, and some great thinking about how they could be used. Is there an education role for libraries in helping patrons use this new technique for connecting to information?

WebP, a new image format for the Web

Most of the common image formats on the web today were established over a decade ago and are based on technology from around that time. Some engineers at Google decided to figure out if there was a way to further compress lossy images like JPEG to make them load faster, while still preserving quality and resolution. As part of this effort, we are releasing a developer preview of a new image format, WebP, that promises to significantly reduce the byte size of photos on the web, allowing web sites to load faster than before.

On the heels of the mention here last week of the bounty to add JPEG2000 support to Firefox comes this announcement from Google of a new image format for websites that is supposedly better than JPEG2000. Lots of buzz around this, but not much in the way of commitment to support it yet. I suppose the real test will be whether WebP will be supported in Firefox before JPEG2000…

General Counsel’s Role in Shoring Up Authentication Practices Used in Secure Communications

The major Internet browsers all currently use the Certificate Authority Trust Model to verify the identity of websites on behalf of end-users. (The Model involves third parties known as certificate authorities or “CAs” issuing digital certificates to browswers and website operators that enable the end-user’s computer to cryptographically prove that the same CA that issued a certificate to the browser also issued a certificate to the website). The CA Trust Model has recently come under fire by the information security community because of technical and institutional defects. Steve Schultze and Ed Felten, in previous posts here, have outlined the Model’s shortcomings and examined potential fixes. The vulernabilities are a big deal because of the potential for man-in-the-middle wiretap exploits as well as imposter website scams.

Is ‘https’ and ‘SSL’ as secure as you believe it is? These researchers point out that it is only as good as your trust in the Certificate Authorities to issue SSL certificates to the appropriate web site owners and to keep safe the secrets necessary to make ‘https’ work. Read this so that you have an informed sense of how secure your communications on the web actually are.

M.I.T. Weighs Charges for Online Lectures

The Massachusetts Institute of Technology has announced that it is considering charging for access to online lectures and class notes, which are currently available free on the Web. Speaking at the Organization for Economic Cooperation and Development’s Institutional Management in Higher Education conference in Paris this month, Lori Breslow, director of M.I.T.’s Teaching and Learning Laboratory, said that free access “may not be the best economic model, so we are now looking seriously at new e-learning opportunities.”

I only saw this brief mention of this in the New York Times. Were MIT seriously considering reversing its ground-breaking course to open up access to its lectures, I think there would be more talk. Maybe I missed other discussion, but if this turns out to be the case then the open courseware movement has been dealt a serious blow.

QR-Code pointing to DLTJ

Tom emphasized the need to have an activity that is relevant to the technology. As he put it, “Use the technology to ampliy the activity.” In this specific case, the 2-D barcodes pointed to text, pictures, and videos that provide additional background to the components depicted in the World War II Memorial. As participants mentioned in the video, it is a way add context to the experience of walking through the memorial.

I had one minor quibble with the execution of the project. The presenters were using EZcodes, a 2-D barcode format licensed exclusively to ScanBuy rather than the emerging de facto QR codes. The problem with EZcodes is that what is encoded is an identifier that is translated by the ScanLife smartphone app to the final destination. By contrast, a QR code has the actual content — a short snippet of text, a URL, a phone number, etc. — actually encoded in the barcode. With an EZcode, the application on one’s smartphone has to look up the value of the identifier at ScanLife’s service before going to the final destination. With a QR code, the smartphone application can go right to the destination website.

The EZcode/Scanbuy scheme has privacy and sustainability issues. First, according to the terms-of-service for the ScanLife reader, each reader application is assigned a unique identifier; because the application must contact the ScanLife with the 2-D barcode identifier to find the value behind the identifier, ScanLife knows everything you scan. Secondly, the ScanLife server is a mandatory intermediary in the process, so if ScanLife goes away all of the barcodes become worthless. This is somewhat similar to the problem with music encumbered with digital rights management; if the server is unavailable, the music file is worthless.¹ QR codes, though, since the data is encoded in the barcode itself, does not have either of these problems.

The text was modified to remove a link to http://www.rcet.org/dvcproject/geohistorian.html on February 11th, 2011.

Footnotes

1. See, for example, DRM sucks redux: Microsoft to nuke MSN Music DRM keys, and also how Wal-Mart Reverses Decision To Shutdown Digital Music DRM Servers.