The Boston Diaries

The ongoing saga of a programmer who doesn't live in Boston, nor does he even like Boston, but yet named his weblog/journal “The Boston Diaries.”

Go figure.

Tuesday, September 11, 2018

A view from the Ft. Lauderdale Office of the Corporation

The building was trembling. This isn't unusual as there's a railroad running along side the building. But what was unusual was the lack of a train. Then a loud thud and finally silence. A few of us looked out the window.

[We might want to get Reba McEntire and Michael Gross on the phone in case this happens again.]

There, in a freshly dug trench that didn't exist moments earlier, was a dead graboid. It must have slammed into the foundation of I-95, which runs along the other side of the building.

Some notes on project names at The Ft. Lauderdale Office Of The Corporation

I was asked about the projects I've mentioned on the blog by a fellow cow-orker, D, and I thought I should summarize them.

First is “Project: Wolowizard.” This used to refer to the entire suite of programs my team (that is, the team I work on, not the team I manage—I'm not a mangager) is responsible for.

Then I wrote “Project: Sippy-Cup to interface with the new hipster hotness. This ended up calling into the same backend as “Project: Wolowizard.” So now it seems silly to consider the backend as part of “Project: Wolowizard” when it's used by two different front ends (the other frontend interfaces with The Protocol Stack From Hell). I'm now going to refer to the common backend as “Project: Lumbergh” (it makes sense if you know the actual name of the program).

And that leaves “Project: America-­On-­Line-­Instant-­Messenger,” the latest program to be written. My fellow cow-orker T gave it its initial name, but no one, not even he, really liked the name. After some discussion it was renamed, and thus I'm giving it a new name here in the blog—“Project: Cleese” (which again, makes total sense if you know the new name and the context in which it was named).

There are some other programs we're responsible for, but as they are rarely touched I'm not going to bother mentioning them. It's mostly legacy stuff anyway and they will most likely go away when The Protocol Stack From Hell is sent back from whence it came (and believe me, it can't happen soon enough).

Obligatory Picture

[“I am NOT a number, I am … a Q-CODE!”]

Obligatory Contact Info

Obligatory Feeds

Obligatory Links

Obligatory Miscellaneous

You have my permission to link freely to any entry here. Go ahead, I won't bite. I promise.

The dates are the permanent links to that day's entries (or entry, if there is only one entry). The titles are the permanent links to that entry only. The format for the links are simple: Start with the base link for this site:, then add the date you are interested in, say 2000/08/01, so that would make the final URL:

You can also specify the entire month by leaving off the day portion. You can even select an arbitrary portion of time.

You may also note subtle shading of the links and that's intentional: the “closer” the link is (relative to the page) the “brighter” it appears. It's an experiment in using color shading to denote the distance a link is from here. If you don't notice it, don't worry; it's not all that important.

It is assumed that every brand name, slogan, corporate name, symbol, design element, et cetera mentioned in these pages is a protected and/or trademarked entity, the sole property of its owner(s), and acknowledgement of this status is implied.

Copyright © 1999-2024 by Sean Conner. All Rights Reserved.