Underlying Conditions

Figure 1. Two-track easement rising to the upper plot south of Wonder Hollow.

The two-track easement I mentioned a couple of posts back angles on a more or less straight line from NNE to SSW, bending ever so slightly where the grade steepens from driveway to an off-road pitch of what I’d guess is at least 25 degrees. I asked the former owner how long the two-track carved a line up the easement, and he said it had been there as long as he could remember, which I’d guess goes back to maybe the 1950s when he was growing up in the then-newly-constructed bungalow (which dates to 1948). The easement links the end of Rosemary Road and the 10 acre plot just above the holler. The legal description includes the exact coordinates for the two-track, noting its 20-foot width, noting it persists only for as long as that upper plot is owned by the same family. And then there is a code in Virginia, 55.1-305. Enjoyment of Easement, which conserves the ways the easement can be used. No converting it to a raceway; not sure it could be paved or significantly upgraded. The code begins, “Unless otherwise provided for in the terms of an easement, the owner of a dominant estate [neighbors] shall not use an easement in a way that is not reasonably consistent with the uses contemplated by the grant of the easement, and the owner of the servient estate [us] shall not engage in an activity or cause to be present any objects either upon the burdened land or immediately adjacent to such land that unreasonably interferes with the enjoyment of the easement by the owner of the dominant estate.”

When it rains, the easement two-track gathers and delivers torrents like a dried up river bed subjected to a heavy downpour. At the bottom of the two-track is our front shed, and until last fall when we had an excavator operator dig below the shed’s foundation wall and then go over it with a sealcoat, laying drain tile, and backfilling with gravel, it didn’t take much rain to send puddling across the shed’s slab, soaking everything that touched the floor. The excavation work successfully redirected the intense runoffs, and now the shed floor stays dry, though the two-track still switches from dry to gushing every time it rains. Erosion spills snaking routes onto the driveway below and exposes a rocky subsurface all along the two-track. Can’t imagine driving a basic passenger vehicle up it all that often. You’d feel tossed-about, and you’d worry about the brakes. I haven’t tried it before, but my guess is it’d feel unsafe. It does fine with small tractor or rugged vehicles like four-wheelers , not that we have anything like that. With each subsequent rain, the ground gives to the water course silty bits of itself, clay particulate, organic material, dust. I couldn’t guess how many times the easement has had to be repaired since the 1950s, nor how many times it has washed out, nor how many small rinses it takes to render it impassable, nor how many licks it takes to get to the center of a Tootsie Roll Tootsie Pop.

Just as the two-track divides Turkey Slope, erosion and deposition, the weather, and vegetative growth cycles participate in shaping the field, sometimes bringing to the surface reminders and remnants, those underlying conditions that through time form a crust that lasts for a while, enduring but changing, transforming while seeming to stand still. “Underlying conditions” come up briefly in Lorrie Moore’s 2023 novel I Am Homeless If This Is Not My Home. There is much, much more to layer on about the book, but for now, let’s just say it is a living-dead travelog, with its protagonists, Finn, who is alive, and Lily, who is dead but talking and otherwise behaving as-though alive, making their way across the midwestern United States and, as they go, negotiating their old relationship, decaying flesh, and the real risks felt to occasionally blinker into the surreal plot. At one of the lodging stops along the way (a bed and breakfast, sort of), the novel hints at chronotopic laminations, “the dispersed, fluid chains of places, times, people, and artifacts that come to be tied together in trajectories of literate action along with the ways multiple activity footings are held and managed” (180). Moore’s novel characterizes the boarding house this way: “Memories from another time and other people in the form of humidity saturated the place. Any given time always had other times beneath it” (161). Could be the slow reveal of the rock bed underlying the two-track, could be the crumbling granite everywhere underfoot in these Blue Ridge mountains, could be that feeling of aging, at home, at work, everywhere you go. But that line has traction; it catches and holds: Any given time always had other times beneath it.

Any given time always had other times ahead, too. Witnessing this capacity, or recognizing these times beneath and times afore, is something close to temporal bandwidth, ฮ”T (in conceptual light more than a formulaic one). I don’t know what will become of the two-track. Can’t predict whether its run-offs will become more fitful until water and gravity prevail. Maybe it becomes a pristine road, as humans love to create roads and then to travel on them (notwithstanding that this occludes much of what is beyond the sensory margins of the road and its immediate surrounds!). To grant this path ephemerality itself as an underlying condition is, I suppose, similar to acknowledging the impermanence of everything. Gone-noting intersects with temporal bandwidth, and maybe even underwrites it.

I also don’t know what will become of the academic field where I have lingered for half of my life. It is changing, in some respects trending kinder and more humane, in some ways trending farther spun-out and dissolute. But trends, too, have a way of doubling back, so we have to keep checking, asking whether we are still becoming kinder and more humane, asking whether we are even listening to and reading one another any more. Yesterday, summer solstice, I saw online a social media post from a senior, now-retiring scholar in the field who was trying to rehome something like 500 books from a long and prosperous career. His conclusion, “no one wants them.”

For a couple of entries now, I’ve been hinting at Wendell Berry’s poem, “IX,” as a low-key motivator for these few meandering thoughts on fields. The poem is reprinted in full, with permission, at The Writer’s Almanac. I’ll share a small excerpt, but you can click over and read the rest, if you want to.

IX.

I go by a field where once
I cultivated a few poor crops.
It is now covered with young trees,
for the forest that belongs here
has come back and reclaimed its own.

Excerpt from Wendell Berry, “IX”


In Dribs and Drabs

And the old blog gets another new entry. It runs, though much is stuck. Garage floor rag for gas cap, as if there was fuel to from sloshing. Comments work, somewhere under the hood chewing and taking one helluva long time to post. Human-check captcha device broke, left behind versions ago. Latest comments widget broken. On this day, broken. Wordcount javascript whatever that was, broken. These among the irreparable few. And the last touch to get things going again involved replacing the script-assigned permissions upon publishing, for folders dropping 0777 to 0775 and for files flipping from 0666 to 0664. Eleven replacements and file overwrites in all so that host and republished entries and archives were harmonious again. It’s not sustainable, or rather, not long-sustainable. Sustainable only ever meant for-now-sustainable, anyway.

Last entry made it to IFTT->Twitter. But atom/RSS never seems to have fired, even though XML structure should be hospitable. As such, this amounts to another turn of the key, making sure exhaust reaches exhaust pipe for predictablish circulation.

Breaktest

An old blog breaks down. Stops working. Fails to grant access to even the control panel, not that anyone remembers the username and pissword, anyway. There’s bondo in the basement, duct tape in a kitchen junk drawer (no, the other junk drawer; the junkier drunk drawer). And then there’s some crappy old untended website with versions galore of Movable Type. Yeah, that same Movable Type from over a decade ago. It’s still wheezing around on the internet. Right here! Version 5.2.13. I had to delete a bunch of tags to get it running. Much of it probably doesn’t work. Comments? They probably return errors. When a blog is rattling around with fewer effs to give than ever before, well, whatever there is, work with it. It was always enough before. Why not now?

And if this shows up online? Breaktest passed.

Coding the UWC

I’m not the nimblest programmer, and because I can count my successes with PHP on one hand, I feel compelled to document them, to extend and preserve them through self-congratulatory accounts like this one.

I am working this semester as a faculty consultant to the University Writing Center. I probably mentioned that before. Basically, my charge is to get online consulting systems up and running at EMU, provide a few months of support and training, and spread the word. The main piece here is asynchronous consulting via email. Much like what we built at Syracuse, this process relies on a form. The student fills it out, uploads an attachment, submits it. The submission calls a PHP script, which in turn displays a You did it! message, a readout of the form data fed to the screen (for saving, for verification), and an email message that routes the form data and the attachment to a listserv. The listserv consists of a handful of subscribers who will comment and send back the uploadeds in turn, in time.

The system works reasonably well, but managing the queue can become a headache. Whose turn is it? At Syracuse, the queue was filled in with four or five rotations, and then as form-fed drafts arrived, consultants would access a shared Google Spreadsheet and manually enter a few vital details: name, email address, time received, time returned, and turnaround (time returned minus time received). These few crumbs of data were helpful, but many of the trackable-sortable pieces of the form were not otherwise captured systematically.

Until Zend Gdata. With this installed, it’s now possible to run a second PHP process that will push all of the form data into a shared Google Spreadsheet automatically. I puzzled over this on Friday, figured it out on Saturday. My initial stumble was that I was trying to integrate the new PHP code into the script that turned out the email and screen readout. Didn’t work. But then I figured out that I could instead route the form to a relay file (I doubt this is what programmers would call it, but I don’t have the vocabulary to name it anything else). The relay file was something like simple.php.

Simple.php is a script with a couple of lines: include formemail.php and include formtospreadsheet.php. Now, when the form gets submitted, both scripts run. The email routes the document like it should, and the Google Spreadsheet (queue) grabs a new line of data. The only element requiring manual entry is the time the consultant returned the commented draft. The shared spreadsheet does everything else: calls the list of consultant names from another page, calculates the turnaround, and records a comprehensive record of who is using the service, the classes they come from, etc. Over time, the comprehensive record will allow us to sort by different classes, different faculty, different colleges, which will help us identify patterns that might prove insightful for how writing is assigned and taught across the curriculum.

I should add that our recent launch of the service limits it to four targeted programs. This is necessary because we are not currently staffed to handle a deluge of submissions, and while we do want the service to get solidly off the ground this semester, we want foremost to extend it to a segment of the 17,000 students who are enrolled in some sort of online class.

PHPinally

We’re experimenting in the WC this semester with consultation by
discontinuous email
. Students can upload up to five pages of whatever they
are working on, the draft then zigs and zags (taking two lefts and then a
right?) through the internet to a listserv account where five always-on
consultants take turns commenting and returning drafts, usually within 24 hours
after the draft is sent. The system seemed to be working fine until recently
when we realized a flaw in the design of the upload form. Basically, the
form allows students to 1.) upload a file or 2.) copy and paste a chunk of text
into the form. ‘Submit’ The form then calls up a PHP script, which, when
there is an uploaded file, puts the file in a temporary directory, builds the
email message to the listserv, attaches the file, sends the email to the
listserv, and finally clears the file from the temporary directory. That much
seemed to be working fine for, oh, ten weeks, and we have 45 such consultations
to show for it. But:

Continue reading →

Et Alia

Several days immersed in lines upon lines of works cited entries may
cause you to wonder at some of the lesser noticed codes that rustle around at
the ends of scholarly articles. A paradox of citation is that the works
cited–a roster of references–flattens out the dimension of each
reference and orders the list arbitrarily according to the alphabet while also
downplaying a surprisingly uneven terrain of mismatched details more pocked than the
face of the moon. This contradiction is forcing me into decisions I hadn’t
expected to be so difficult.

The et al. is one example. It allows the keeper of the works to abbreviate,
to shorten a list of authors so that any source with more than three authors can
be listed alphabetically by the last name of the lead author followed by et al.
It is a note of inclusive omission. And I suppose it made greater sense in an era
when works citeds, rife with formulaic peculiarity, were typed on a typewriter.
The et al. conserves characters; it shortens the list of names, leaving off
everyone but the primary author. It is no coincidence that et al. rhymes with economic al. So what is the big deal?

Continue reading →

Trouble Shot

Even if the following fixes are only useful to one or two people, posting
them to the blog makes them differently available for searching and bookmarking.
Since I installed MT3.34, I ran across a couple of small snags. Nothing
too off-putting, really. Just bumps along the up-gradual way.

First, the new tagging features in MT3.3+ are, as I’ve said before, really
slick. But I was having trouble with the interface that allows me to merge
tags. Say I have two tags I want to merge, like "method" and "methods."
Okay? I click on one or the other and I the tag becomes editable. After I
apply changes, I can select "Rename," in which case it will summon the database
to see if the new tag already exists. If it does exist, a java popup asks
whether I want to proceed with the merge. If the revised tag doesn’t
exist, it goes ahead and applies the change. The other option, "cancel,"
does just that. Simple, eh?

Continue reading →

Up- or Down- A Grade is a Slope

It was upgrade weekend for the blog, meaning I had my eyes turned under the
hood and my fingers in the blog code Friday into Saturday (today, all reading,
responding, and figuring grades).

I was running MT3.2, growing every day more envious of those who were putting
to use the tagging features built into 3.3+. The upgrade was a cinch.
Just FTPed the files into place and logged in. The config file didn’t need
any changes. Well, it didn’t require any changes, that is, until I also
converted the database from MySQL4 to MySQL5. For that, I had to add a
DBSocket line to the config file. I had not a clue about it at the time,
but the support folks at icdsoft.com are remarkably good.

That’s a hearty new cumulus tagcloud over at the left. There’s a lot to
be said for MT’s tagging features built into the latest versions. Now I can merge
tags across the entire weblog, sort by tags (for editing or adding new companion
tags), and grade the tags with a max="x" setting. That’s the statement I use
to come up with ten levels for the tag cloud. And I’ve set the CSS to
display:none for the bottom five (#6-10). That way only the top five levels show
up, and the cloud isn’t the size of Lake Michigan.

Continue reading →