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).

Sunday, September 16, 2018

Before the Pink Panther there was Peter Gunn

Bunny has been binge watching “Peter Gunn” and I have to say, the music is fantastic! The only other TV shows that had as jazzy a score were “Twin Peaks” and “Cowboy Bebop.” I wish more shows used a jazz sound track, it's fun just to listen to the music.

Tuesday, September 18, 2018

This is why I tend towards writing my own code libraries

Six years ago I had the need to fetch an image via HTTP as part of testing “Project: Lumbergh.” At the time, I thought You know what? Why don't I use libcurl? It's installed. It's supposedly easy to use. It'll save me the hour or so it'll take me to write the code to connect to the server, send the request and read the reply.

It still took about an hour, mainly to figure out how to use the darned library. But it worked.

And then I went to test on Solaris (which is what production runs on) and well …

r2839 | spc | 2012-07-11 14:22:27 -0400 (Wed, 11 Jul 2012) | 8 lines

[Testing]

It's amazing what isn't installed on Solaris.

And yes, I do use curl for testing. Easy (if insanely large) library to use to snarf down web requests.

I had to download libcurl and check it into the repository because it's not on Solaris.

And then I had to figure out the special ./configure options to get it compiled under Solaris.

And then I had to wait for ./configure and make to run (and on Solaris, this is a S—L——O———W————P—————P——————R———————O————————C—————————E——————————S—————————————S).

And then I had to figure out how to integrate this into the build system for Solaris.

And for something that was supposed to be “easy to use” turned out to be not so easy. Nor quick. And has been a thorn in my side these past six years.

Seven years ago I wrote a Lua module to generate hashes. Instead of pulling the code from various RFCs, I thought I would link to OpenSSL, since it already included the code for the various hashes, and who knows—it might even be optimized.

This only took a few moments to implement and was rather easy.

Until Apple decided to deprecate the use of OpenSSL on Mac OS-X and later remove OpenSSL in their latest offerings.

I use said Lua module at work.

We mostly develop under Mac OS-X.

Sigh.

This has become a thorn in my side over the past few years. The issue came up two weeks ago when my fellow cow-orker TS, decided to update his Mac OS-X laptop and the build broke. And it came up today because my other fellow cow-orker TS-II (same initials—go figure) did some update or other on his Mac OS-X laptop and the build broke, but in a different way (wow—to think that each version of Mac OS-X is a special snowflake).

Two libraries, used to avoid the whole “Not Invented Here Syndrome” and to speed up development.

In both cases, it has not speed up development. It has slowed down development as I've had to find more and more ways to keep using these infernal libraries.

I guess I'll spend a few hours ripping out libcurl and OpenSSL and replacing it with code I've written to speed things up around here.

Obligatory Picture

[It's a study in contrasts—digital camera contrasts]

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: http://boston.conman.org/, then add the date you are interested in, say 2000/08/01, so that would make the final URL:

http://boston.conman.org/2000/08/01

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-2018 by Sean Conner. All Rights Reserved.