Decommissioned

Hit and Miss #250

This week saw the formal end of life of two software products—both were famous, for a time, before ending their lives more or less infamously.


First, Internet Explorer. Microsoft’s announcement of its eventual demise spawned a countdown site and the decommissioning itself spawned a hilarious gravestone. I particularly enjoyed Dave Rupert’s reminiscences on the browser—they reminded me of not-so-long-ago conversations as a developer about supporting IE.

Even once decommissioned, there’s a long, long tail in browser usage: a few years ago, reviewing analytics for a government site at work, we found a small but consistent level of visits from Internet Explorer 6, even then an unsupported version; they all happened during work hours, and the pages visited were public-facing, leading us to think the browser was still installed on some kiosk in a small office, to browse the department’s pages.

Though now long loathed, it’s worth acknowledging—perhaps begrudgingly, for some—the web tech innovations that came originally from IE.


Second, COVID Alert. Friday, Canada’s exposure notification service was formally decommissionedtwo years less a day since it was first announced. (I remember the latter day well—I’d been tied up in a call with our team of lawyers during the announcement, emerging eventually for lunch, at which point my then roommate said, “So that’s what you’ve been working on!”)

While it started with a bang, it ended with a quiet fizzle. If you’d ever installed it, you likely long ago uninstalled it (no judgement from me if you did!). Some of the highest profile public discussion in the last few months has been Bianca Wylie’s eight-part series on the app, working from the outside to understand and advocate for its decommissioning—starting in April, when Bianca wrote about political accountability for technical solutions.

My journey with COVID Alert has been a long, long road. I helped propose and launch the service, spent some time away from the team, came back in the midst of heavy feature development for a possible evolution of the service, and had the honour to observe its decommissioning (I had very little to contribute at that point!). Launching a national service is a wild ride—I loved it, it inspired me, and it nuanced my perspectives on digital government and civic tech. I got to witness and share in incredible accomplishments from my colleagues, truly a privilege. There’ll be more written and shared about the service in the months ahead, by myself and others.

For me, it’s a lot of feelings, hard to sort out—as it has been the entire journey. The pandemic has changed in many ways since we started, but working on the service was inextricably tied with COVID-19, including our working conditions. I remember a cautious park meetup in June or July 2020, to say farewell to a colleague, during which a number of us had a testing version of the app installed on our phones. While we joked darkly about using the app to notify one another of exposure if we later tested positive, it’s humbling to look at the case counts (and evolution of the virus) then versus in the years (!) that have followed, to think of just how “good we had it” back in that first pandemic summer.

No doubt I’ll have more to share—some publicly, some privately—in times ahead. But I wanted to close with a few links to public information about the service, information I’m very glad to see out there:

It was a privilege to work on the service, to grow through doing so. Friday’s announcement signalled the end of a long-held breath—one I’m very glad to have been able to exhale. I imagine it was the same for those who worked on Internet Explorer’s many versions. Building software (or policy around it), you never quite know what the impact of your work will be—eventually, you’re likely happiest to see it wound down and given its proper rest.

All the best for the week ahead.

Lucas