Presentations

Here is a small bit of advice which has served me well for years: if you are given an opportunity to speak in front of others, treat that opportunity as a rare privilege. Don’t dread it; use it to make a small change in the world. If your ambitions run closer to home, use it to make a big change in your life. Make it worthwhile.

Design: Bleak House Revisited

Trying my hand at book cover design with a classic.

Revisiting the classic

This is a difficult one to capture with a cover. The tone, themes, and plot do not necessarily match the title, but the book is so full of life and characters that anything short of a parade fails to capture its vitality. With this design I am leaning into the title itself.

Other designers appear to have made the same choice with this one.

I’m much more fond of the Vintage and Penguin editions below, however. These are much more engaging and do a better job of capturing the story’s themes in a glance.

I still have a lot to learn about cover design, but I think this is a pretty OK first outing. Authors: if you’d like to work with me on a design for your book’s cover, get in touch!

The Lost World of the Naturalist

This week I am reading a classic naturalist’s work, Edwin Way Teale’s North With the Spring. This book is a must-read for anyone interested in Florida nature, but it should also be near the top of the list for anyone interested in how to be a naturalist. I picked up the book for the former purpose, but found myself enthralled by the latter. As an aside, this is one of the many ways I am enriched by breaking bread with the dead. I approach every book with an idea of where it will lead me, but I never end up in that place. Recent authors don’t often take me too far from the path I picture through the book, because we have shared many of the same experiences; going back only as far as fifty years, though, leads to wild and wonderful (and often chilling, challenging, and vexing) places.  

I entered North with the Spring with a historian’s interest in how Teale thought of Florida in the 1940s. His idea was a compelling one: starting somewhere at the southern tip of Florida, he would follow the spring as it made its inexorable way to the wintry northland of New England. The book was popular in its day, and it has endured long enough in library stacks to have inspired others to retrace the path Teale took up the spine of the seaboard. I started the book with a research goal in mind, but I was immediately blown away by how Teale lived – and how different it is from the way so many of us live today. In contrast to our capsular civilization of AirPods, air conditioned and noise-canceling car interiors, tightly closed and carefully climate-controlled offices and apartments, Teale describes a way of living close to nature, constantly listening, looking, smelling, and most of all, responding.  

Here is an example. “Each morning,” Teale wrote of the “pre-spring days” early in his journey, “we awoke while it was still, to the steady throbbing of fishing boats moving out among the Ten Thousand Islands of the Gulf.” Awakening further, Teale described a rush of sensory information. “With the earliest daylight,” he continued, “came the strident alarm-clock of the red-bellied woodpecker amid the palms outside our cabin….” Stepping outside into the cool February morning, Teale and his wife found “exciting new odors… all around us in the perfumed air of the dawn.”  

I read this and think about my morning routine. I awaken in a sealed room. I do not hear birds. A ceiling fan whirrs overhead, quietly humming, while a tower fan drones on the other side of the room. The air conditioner hums through the ducts. Another fan spins noisily in the mint green heat exchanger supporting the air conditioner just below the bedroom window. In the bathroom I am beyond the sound of the fans, but still comfortably sealed within.  I hear the nearest songbirds—a dueling Cardinal and Carolina Wren at this time of year– whistling their morning tunes from magnolia trees outside.   

In contrast with Teale, I am distant from nature. I am almost hermetically sealed in my capsule.  

While driving, Teale noticed plants along the roadway, changes in the communities of birds flocking overhead, minute details about the weather, small sounds, flashes of color. Taking a detour near Waycross, Georgia on the way down to the Everglades, he reported: “As we reached a stretch of swampy woodland, a storm of sound assailed our ears. All the trees were alive with blackbirds. Thousands swarmed among the branches, filled with the excitement of migration time. They were incessantly in motion, hopping, flying, alighting, combining their voices in a deafening clamor.”  

I do not remember the last time I heard a “deafening clamor” of migrating birds outside my car window, and I suspect I am not alone. I look around and notice that the windows of every car around me are tightly sealed. We move through the world in capsular isolation. Meanwhile, Teale’s attention to the natural world was unaffected even by the clattering iron of rail travel. “If you come north by the train in midspring and have an ear for the swamp music of toads and frogs,” he explained, “you will become aware of something interesting. You seem to be running backward in time. As the spring becomes less and less advanced as you go north, you begin with the latest-appearing of the marsh-callers and progress backward to the earliest of the peepers.”  

I am reading Teale’s account of the coming spring sunburnt and muscle-sore from a long paddle down the Wakulla River last weekend. For Teale—at least the character he plays in North With the Spring—nature was the substance within which life unfolded, inseparable from daily existence. For me, it is a commodity to be consumed. I engage the natural world fresh from the sporting goods store like a student joining the intramural league. The commodification of nature is nothing new, of course. David Nelson shows, for example, how the Civilian Conservation Corps and Florida business interests worked together to develop the modern tourism industry in the Florida Park System.  

Still, I can’t help but think that the separation of human from nature is rapidly and irreversibly accelerating. Teale drove with the windows down because his car didn’t have an air conditioner. Would he drive with the windows up today, podcast blaring? He heard frogs and birds from the windows of Pullman coaches because that was how people traveled across the country at that time. Would he put on his headphones and watch a movie on the plane at 35,000 feet today? He woke to the sounds of boats and birds in the Ten Thousand Islands because open windows were the only way to cool the room. Today, like the rest of us, he would probably wake up to the roar of the air conditioner beneath the hotel window blowing ice cold air into the room.  

These are things I don’t want to give up, but North With the Spring reminds me of the beautiful, natural things I have give up in exchange for comfort.   

Assume the Documentation is Incomplete

Here is a simple lesson from today: assume the documentation is never complete and plan accordingly.

I lead a small team responsible for supporting, maintaining, and developing enhancements for a complex IWMS (that’s Integrated Workplace Management System for the un-jargonated) used by the State of Florida to manage facilities. Though the state has only been using this system for about five years, it has been around for almost twenty years—and it shows. Every decision made by designers over the years, influenced as they have been by every passing fashion in web apps development, has left a residual mark on the system. There are some areas of the system where these marks are more apparent than others, but we run into them in unexpected ways every day. Perhaps coincidentally (but probably not) these little beauty marks are also the least documented portions of the system. Today, we encountered one while we were trying to figure out an alternative to the antiquated way this system handles data integrations through the API. The system uses a dummy user account, subject to the same password policies as the rest of the system, to update data. This means that we need to either, a.) change the system-wide password policy, which may make sense but we haven’t considered doing yet; or, b.) someone needs to provide new service credentials to agents using the API on a regular basis. As always, we asked: hasn’t someone else solved this problem already? Turning to the system documentation turned up no results, and this system is too niche for Google to turn up many useful results. As usual, then, we were on our own to find a workaround. 

I felt a little thrill when I noticed a “Service Only” flag on user profile pages. Someone, somewhere must have come up with a solution for service accounts, I thought. Maybe this flag overrides some of the system security policies used to protect human user accounts from the humans who use them! If browsing the documentation by topic and searching the contents for “API credentials” and variants didn’t work, at least this little flag clearly visible on the screen would be described somewhere and get us closer to an answer. 

That was not the case. The “Service Only” flag was not described anywhere in the system documentation. Undeterred, we did what intrepid developers and admins everywhere would do in this situation: turn it on and see what happens. We fired up the test environment, created a throwaway account, and made our way to the screen where the little flag lives–only to find that it is a read-only field. We could not turn it on. 

Fine. In this no-code system, if all else fails, you can dig into the data model, form elements, and queries to understand by inference how things work. We delved into the form and data model to find – nothing. The boolean flag simply exists in a read-only state. There are no workflows attached to it and no associations leading to or from it. 

Is this some sort of vestigial feature leftover from old versions to support legacy accounts? Can it be activated through some obscure menu somewhere else? Who knows? It’s not in the documentation.

I draw a few, interrelated lessons from this.

  1. As an administrator, never assume the system documentation will have the answer you need. In the absence of holy writ from the vendor, develop procedures to mitigate your own ignorance.
  2. As a developer, write. better. documentation. What’s there is never enough. Sure, writing documentation may not be your job, but at some point it will be your responsibility.
  3. If it’s your job to write documentation, go through every button on every screen. Assume you have never written enough and give this assumption some weight when you decide how much more work to do before release.
  4. As a support provider, give users the ability to suggest improvements right in the documentation. “Contact Us” on the page isn’t enough. Users don’t want developers to cede their authority by deploying a wiki, but some of the features of a wiki should be more widespread. I think the “Talk” pages on Wikipedia are a great solution for user feedback on documentation.

Here’s a good song to end the day. That “Walk On By” sample was all over the place back in the 90s, but this is a unique one.

Google Bard’s Gothic Hallucinations

Yesterday I asked Google Bard the kind of question I’ve often wanted to ask a search engine.

Imagine you are a professor preparing a graduate seminar on 18th- and 19th-Century British Gothic Literature,” I instructed the machine. “What materials would you place on the syllabus, including a combination of primary texts and secondary criticism and interpretation, and how would you group them?”

This is a complex question, but the solution—as I understand it—should just be a series of search queries in which the most appropriate results are mapped into the LLM matrix to produce the output. Because Google is the market leader in search, and I’m not asking Bard to display its “personality” like Bing/Sydney (the “horniest” chatbot, as The Vergecast would have it), I thought this would be an ideal task for Bard.

Boy, was I wrong. Here is the syllabus Google Bard produced.*

On first glance, this looks like a valid, if unoriginal, syllabus. Bard has identified some representative primary texts matching the query and has chosen to present them chronologically, rather than thematically. That is a sane choice. And those texts actually exist.

Now let’s look at the secondary literature Bard wants students to grapple with. Bard has selected the following texts:

  • David Punter, The Gothic Imagination: A Critical History of Gothic Fiction from 1764 to the
    Present Day
    (1996)
  • Anne Williams, Gothic Literature (1994)
  • Stephen D. Gosling, Gothic Literature: A Cultural History (2000)
  • William Veeder, Gothic Fiction: A Critical Introduction (2005)
  • David Skidmore, Gothic Literature (2013)
  • Andrew James Smillie, Gothic Literature (2017)

“I would… group the secondary criticism and interpretation chronologically,” Bard says, “starting with Punter’s The Gothic Imagination, the first comprehensive critical history of Gothic fiction, and ending with Smillie’s Gothic Literature, the most recent critical history of the genre.” That sounds good, but none of these texts exist. Not one. Google Bard made up every one of the texts on this list, and several of the people listed there as well.

David Punter is, indeed, a scholar of gothic literature, but as far as I can tell has never produced a text entitled The Gothic Imagination: A Critical History of Gothic Fiction from 1764 to the Present Day. Anne Williams is Professor emeritus in the English department at UGA, but I cannot find an overview by Williams published in 1994 (though Art of Darkness:  A Poetics of Gothic, published in 1995, sounds fascinating). I can find no gothic scholar named Stephen D. Gosling, and obviously no cultural history Gosling may have authored. William Veeder was a professor at U. Chicago but never wrote Gothic Fiction: a Critical Introduction. And so on. None of these books exist.

Make of this what you will. I don’t think Bing or ChatGPT would do much better at this task right now, but it is only a matter of time until they will be able to deliver accurate results. In the meantime, the machine is confidently hallucinating. Caveat emptor.

Of course, I did ask Bard to “imagine” it is a professor. Maybe it took me too literally and “imagined” a bunch of books that would be great for graduate students to read. Perhaps I should have told Bard it is a professor and insisted that it deliver only real results.

There’s always next time.

* To be fair, Google warned me twice that this would happen.