Just over twenty years ago, computer scientists were racing the clock to fix a possibly devastating error brought about by an over-estimation of the pace at which tech becomes obsolete, which is an over-estimation of the pace of change itself. It turns out that one of the two popular solutions to the problem made the same mistake. And now we’re paying for it, but mainly through some annoyances, not the sort of world-stopping calamity that the prior error threatened.

The problem twenty years ago was that software developers had with some frequency thought that storing the year could be done with two digits, so that 1970 would be saved as 70. After all, the program wouldn’t still be used in 2000! Would we also still be driving around on earth-bound cars, or giving poodles ridiculous haircuts? Ridiculous!

But, if those apps were in fact still be used as the new millennium began, then the two digits internally representing the year would be taken internally as 00, which would be likely to confuse a computer that would assume – based on the way numbers work – that 00 (2000) comes before 70 (1970). And 2001 would look like 1901, etc.

One approach developers took to preempt the Y2K (year two thousand) bug was to change the way the programs expressed date data, allotting four digits to the year. We shall call this “the right way.” But it’s more complex than it seems. For example, you may have to find every place in a complex, integrated set of programs where the date is referred to. You may have to recompile ancient code, unearthing compilers from ancient crypts guarded by three-headed dogs. It was a freaking nightmare for many organizations.

The second approach was to write a little code that looked for year dates between 00 and 20, and write an except that takes them as referring to 2000-2020. Most applications aren’t dealing with dates going back to the beginning of the 20th century, so that worked. Chris Stokel-Walter (twitter: @stokel) in his excellent, brief explainer in New Scientist, says that an estimated 80% of Y2K solutions took this approach, known as “windowing”, but which we shall refer to it as the “Please don’t do this” approach.

Well, now it’s 2020 and some indeterminate number of windowed apps haven’t updated the fix. Thus, some traffic meters have stopped working. As Chris writes, “The theory was that these windowed systems would be outmoded by the time 2020 arrived…”

So, exactly the same over-estimation of the pace of tech obsolescence has led to exactly the same problem. Surprise?

It’s not at all clear, however, who has made this mistake. The developers implementing the windowing patch were staving off an imminent, plausible crashing of globally crucial systems. Windowing was a reasonable approach to forestalling this crisis … but only if there was a system – a human system – to remember to allocate resources for fixing the problem that the patch postponed.

Conclusion: “Human system” is an oxymoron.

Be the first to comment »

Note that this is not late-breaking news. It’s breaking news brought to you late: Android contains a really great Google transcription tool.

Live Transcribe transcribes spoken text in real time. So far, it seems pretty awesome at it. And its machine learning model is loaded on your device, so it works even when you’re offline — convenient and potentially less intrusive privacy-wise. (Only potentially, because Google could upload your text when you connect if it wanted to.)

You can download Live Transcribe from the Play Store, but if you’re like me, it will only give you an option to uninstall it. Oddly, it doesn’t show up in my App drawer. You have to go to your phone’s Settings > Accessibility screen and scroll all the way down to find the Live Transcribe option.

Once you turn it on, you’ll get an icon all the way at the bottom of your screen, to the right of the Home button. Weird that it’s given that much status, but there it is.

I expect I will be using this tool with surprising frequency … although if I expect it, it won’t be surprising.

Be the first to comment »

The first in a series of six posts about my experiences learning how to train a machine learning system has just been posted here. There’s no code and no math in it. Instead it focuses on the tasks and choices involved in building one of these applications. How do you figure out what sort of data to provide? How do you get that data into the system? How can you tell when the system has been trained? What types of controls do the developers have over the outcomes? What sort of ways can I go wrong? (Given that the title of the series is “The Adventures of a TensorFlow.js n00b” the answer to that last question is: Every way.)

I was guided through this project by Yannick Assogba, a developer in the machine learning research group — People + AI Research –I’m embedded in at Google as a writer in residence. Yannick is natural born teacher, and is preternaturally patient.

The series is quite frank. I make every stupid mistake possible. And for your Schadenfreude, five more posts in this series are on their way…

.

Be the first to comment »

At long last I’m getting around to updating Joho’s look, for several reasons:

First, my last redesign made the page look like it was designed in 1999, although I actually did the redesign about seven years ago, I think.

Second, CSS has made it easy enough to avoid using a table as the container for all of the contents of the page. That was always a hack but, it was easier than dealing with floats, etc., for a multicolumn design.

Third, it was especially easy to move away from using a table because I’ve given up on a multicolumn design. That has meant for now stripping out some early 2000s goodness, including my link-rotted blogroll, categories list, and archives. I plan on adding back my blogroll, if only as an historic artefact, via an overlay.

Fourth, the page page needs to be more readable in the mobile camera phones that the kids all use what with their Facebooking, and Chapnapping, and all the rest. I have by no means done all the work required to make this page truly responsive (Everyday Chaos is my best attempt at employing a modified a responsive template), but I’m hoping it will be responsive enough for the kids who are used to their Facebroking and Snoopchitting and all the rest.

Fifth, Medium.com‘s elegant design redefined what a blog should look like. Yes, that was like 18 years ago, but I was too busy with my Facebokchoying and Schnapssbapping to get around to it. Medium not only transformed our expectations about the tools for writing a post, but also about the reading experience: easy to take in, elegant, content-focused. So, I have increased the font size, removed the distracting sidebar, and I hope made it a more inviting page.

I’m obviously not done. For example, I haven’t yet gotten around to updating the page that shows a single post. But I’m happy so far with the redesign. Or, to put that more accurately, I’m somewhat less embarrassed by the page.

Until design tastes change again.

Aaaand, they just did.

Be the first to comment »

I’ve been a hobbyist programmer since I got my first computer in 1984 or so. I greatly enjoy it and I’m terrible at it.

I mainly use JS to create utilities for myself that take me 1,000 hours to write and save me a lifetime of 45 seconds. I like Javascript for tawdry reasons: It’s straightforward, there’s a huge collection of libraries, any question I might ever have has already been asked and answered at StackOverflow, and I get to see the results immediately on screen. It’s of course also useful for the various bush league Web sites I occasionally have to put up (e.g., Everyday Chaos). Also, jQuery makes dumb HTML (DOM) work easy.

But here’s the but…

But, ECMA is taking JS in a terrible direction: it’s turning it professional, what with the arrow functions and the promises, etc. If you’re a hobbyist who enjoys programming for the logic of it, the new stuff in JS hides that logic on behalf of things I happen not to care about like elegance, consistency, and concision.

Now, I know that I don’t have to use the new stuff. But in fact I do, because the community I rely on to answer my questions — basically StackOverflow — increasingly is answering with the new stuff.

There’s a reason JS became the most used language on the planet: not only can you do webby stuff with it, it has a pretty linear learning curve. Now I literally feel like I’m in danger of losing “View Source” from my browser … literally because while I can view the source, increasingly I can’t understand it.

I’m going to lose this argument. I already have lost it. I should lose it. My position is wrong. I know that. Nevertheless, I stand firmly on the wrong side of history as I declare in my lonely, quavering voice: Keep. JavaScript. Dumb.

1 Comment »

If your Android phone no longer generates tones that work when you’re asked to “Press 1 to … do something” Pixel support says go to Settings > Apps > Phone. Touch the three dots in the upper right, select “Uninstall updates” and restart your phone. Worked for me.

My list of recent calls was preserved. Yay. But presumably Google is working on a more elegant solution.

2 Comments »

My new book (Everyday Chaos, HBR Press, May 2019) has a few hundred footnotes with links to online sources. Because Web sites change and links rot, I decided to link to Perma.cc‘s pages instead . Perma.cc is a product of the Harvard Library Innovation Lab, which I used to co-direct with Kim Dulin, but Perma is a Jonathan Zittrain project from after I left.

When you give Perma.cc a link to a page on the Web, it comes back with a link to a page on the Perma.cc site. That page has an archive copy of the original page exactly as it was when you supplied the link. It also makes a screen capture of that original page. And of course it includes a link to the original. It also promises to maintain the Perma.cc copy and screen capture in perpetuity — a promise backed by the Harvard Law Library and dozens of other libraries. So, when you give a reader a Perma link, they are taken to the Perma.cc page where they’ll always find the archived copy and the screen capture, no matter what happens to the original site. Also, the service is free for everyone, for real. Plus, the site doesn’t require users to supply any information about themselves. Also, there are no ads.

So that’s why my book’s references are to Perma.cc.

But, over the course of the six years I spent writing this book, my references suffered some link rot on my side. Before I got around to creating the Perma links, I managed to make all the obvious errors and some not so obvious. As a result, now that I’m at the copyediting stage, I wanted to check all the Perma links.

I had already compiled a bibliography as a spreadsheet. (The book will point to the Perma.cc page for that spreadsheet.) So, I selected the Title and Perma Link columns, copied the content, and stuck it into a text document. Each line contains the page’s headline and then the Perma link.

Perma.cc has an API that made it simple to write a script that looks up each Perma link and prints out the title it’s recorded next to the title of the page that I intend to be linked. If there’s a problem with Perma link, such as a double “https://https://” (a mistake I managed to introduce about a dozen times), or if the Perma link is private and not accessible to the public, it notes the problem. The human brain is good at scanning this sort of info, looking for inconsistencies.

Here’s the script. I used PHP because I happen to know it better than a less embarrassing choice such as Python and because I have no shame.

Run this script in a browser and it will create a page with the results. (The script is available at GitHub.)

Thanks, Perma.cc!

By the way, and mainly because I keep losing track of this info, the table of code was created by a little service cleverly called Convert JS to Table.

1 Comment »

Operating systems play favorites when it comes to fonts: they pick one as their default. And the OS’s don’t agree with one another:

From https://furbo.org/stuff/systemfonts-new.html

But now when you’re designing a page you can tell CSS to use the system font of whatever operating system the browser is running on. This is thanks to Craig Hockenberry who proposed the idea in an article three years ago. Apple picked up on it, and now it’s worked it’s way into the standard CSS font module and is supported by Chrome and Safari; Windows and Mozilla are lagging. Here’s Craig’s write-up of the process.

Here’s a quick test of whether it’s working in the browser you’re reading this post with:

We now return you to this blog’s regular font, already in progress.

Be the first to comment »

In 2015, I posted about a way to unlock the picture frames that for some reason ship with Keynote but are not accessible within Keynote. They’re there but they don’t show up on the pull down, so you can’t use them.

In 2018, with Keynote at version 8 + change, the same technique works. With the same warnings. So, if you want to give yourself considerably more than the 14 frames that the menu shows you, go here, follow the instructions carefully, and most important: do not blame me. (The replacement file I link to still seems to work.)

Be the first to comment »

Google Docs’ version history functionality is getting to be really powerful and useful. Named versions help tame that power.

Google Docs automatically saves versions as you type so you can roll back to a prior state of your document at any point. In fact, you can roll back, copy a piece of it, roll forward, and paste in text from your past.

But because Google Docs makes so many versions and does so without asking you, suppose you want to go back to a version from earlier in the day before you cut that paragraph about secretly enjoying Paw Patrol? Google labels each automatically-created version with a time stamp, but you happened not to have memorized the precise time you made the change.

Now you can give a friendly name to a version. So let’s say you’re about to cut the Paw Patrol paragraph, but you’re not sure that you should. Before you make the cut, go to File > Version history > Name current version and give it a name such as “With Paw Patrol”. (If you want to be perverse, use the current hour and minute as the time. That’ll get you nowhere fast.) That name will show up in the list of versions under File > Version history > See version history.

Now when you cut the paragraph or make other changes, you’ll always be able to go back.

Meanwhile, Google will continue to automatically create new versions, capturing quite small increments of change. If you want to step back through the changes you’ve made since you named a version, click on the triangle to the left of the current version at the top of the version history.

Also, note that when you click on a version in the version history, it highlights the difference between the prior version and this one.

Note that comments are not saved with versions. Let me put this differently: When you restore a prior version, it will not have any of its comments. This is unfortunate.

Nevertheless, there are some big things not to like about Google Docs, but versioning definitely is not one of them.

Be the first to comment »