To Leave (Un)Changed: Revisiting the Walnut Trees

Returning

On the south side of campus, past my freshman-year dorm, is the Arboretum. The walk there is relatively the same as it was 2 years ago, walking around Onondaga Hall and cutting across the parking lot to the entrance of the Arboretum, being welcomed by the plaque that I’ve never stopped to read. I walked past the lonely bench and the large, old walnut tree with a huge burl. I was a bit shocked to see they’d cut the longest branch of the wide tree. It was roughly three or four times my height in length and sloped down and away from the trunk, nearly touching the ground. One of the first things I’d done while at Geneseo was climb that branch, the only way to reach the rest of the tree. All that remains of that branch is the clean cut—presumably accomplished by some power tool—that had exposed the circular rings and revealed its age.

Trodding Further

I continued to make my way around the Arboretum, veering right once I reached the gazebo and down the slimmer, lesser-known path. The absence of grass leads me to where I intend to go. There are a few twigs, leaves, and wayward bush branches in areas of the path, but it’s relatively clear. The ground was a bit slick with the rain from the day prior, and the air was still tainted with the residual cold, but all things considered, it probably didn’t warrant the winter jacket I’d brought with me.

I watched some squirrels run between the trees, jumping from one branch to another, and how they ruffled the dense layer of leaves that hid the ground below the bushes. A few cardinals and some similarly sized brown birds—maybe chickadees—flew about the area.

The path was short, and I could hear the nearby road on the lower slope of the half-hazard oval trail. The brushing of car tires and the occasional bombardment of a 16-wheeler would drown out the sound of the birds and rustling of wind. It was an odd reminder that this small patch of woods was exactly that—’a small patch’ enclosed by paved roads that have imposed themselves on either side. Even though they were probably hundreds of feet away, the noise of engines still disturbed this apparently ‘untouched’ piece of nature.

The Walnut Tree

I made my way up the rest of the trail. Towards the very end, just before you can see the exit that spits you out on the other side of the gazebo, was an obscenely tall black walnut tree. It was probably the largest in the entire Arboretum. Unlike the ones that greeted me at the entrance, this one has remained untouched, allowed to keep all of its branches.

It’s probably the biggest tree I’ve ever seen. It must have been at least 35-40 feet tall, probably more. I tried to see how far I could wrap my arms around it (a rather uncomfortable task considering the rather deep, dry ridges of the bark, which caught on the cotton of my sweatshirt). At best, I couldn’t even wrap my arms halfway around the trunk.

The tree split into two main branches, both of which split again. The smaller limbs that branched off were curled and hitched in an almost gnarly way. The ends of many of the branches were bare, bark gone. The absence of leaves would probably be cause for concern if it were a few months warmer. Yet, the other walnut tree, the welcoming one that greets visitors before the gazebo, had a giant burl—sometimes indicative of disease. It’s an odd and somewhat solemn reminder that even those giant, imposing branched figures die; they’re susceptible to disease just like we are, even though they don’t show it the same way.

Extremely tall black walnut tree with backpack for scale -- Extremely tall black walnut tree with backpack for scale

Wide photo of the branches of the black walnut tree -- A wider view of the branches of the black walnut tree

Movement

From this side of the trail, I can hear the other road that eventually leads past Main Street. It’s the same howling of tires and the same reminder, mirroring the sounds heard at the other end of the trail. No matter how large the forest, there’s usually some kind of path that will cut through it, whether it be a paved road or a trodden trail. As a group, humans don’t tend to leave a place unchanged; as an individual, the changes I left were minimal—footprints in dirt, microscopic cotton fibers on bark, and a few twigs crunched underfoot—but they’re changes all the same.

As I left the Arboretum and began the rather long walk back home, I reflected on a quote from Aristotle that one of my professors mentioned a few days before, “there is no time without change.” Drawing from this, I’d like to contradict the common poetic sentiment that time seems to stop or slow when you encounter nature. Regardless of perception, time doesn’t stop or slow. There will always be constant movement and change—the cutting of branches, the flying of birds, the trodding of trails, the losing of bark, and the building of roads—there will always be the constant passing of time.

Rooting through Terminal: New Understandings of Technology and Text

New Connections

Before this class, I hadn’t thought much about the relationship between computers and the humanities. I had seen it simply as a tool for drafting/translating works into a digital format, primarily for neatness and assignment submission. Following our classes and our exploration of/introduction to the fluid text edition of Walden (and its accompanying HTML file), I’ve begun to see the greater importance of computers as a tool to make works more accessible. Computers, firstly as machines, enable us to translate manuscripts into a uniform digital version and font that is easily readable by most people. With the aid of servers and programming languages, they enable the creation of websites that anyone can access and, thereby, read works of the humanities. Considering the fluid text edition of Walden, the use of computers/programming enables readers to see the development of the text through its different drafts by isolating the changes (shown through the green words and strikes throughs) side-by-side. Without this edition of the work, which was made possible by computers, readers would have to go one-by-one through each manuscript and painstakingly try to locate all the changes.

Personal Impacts

The most significant impact this course has had on me thus far is how it has completely changed my relationship with my computer–how I approach, think about, and interact with my device. I’ve found myself frequently using Terminal to navigate my computer and make new documents rather than going through Finder, which I’d been doing basically my digital life. In many ways, it’s made small tasks more efficient (not having to go through the opener page of Word before making a new doc or scrambling to save it in the proper file/location at the end of class). Alongside this, it’s also changed how I visualize the form/organization of the computer in my mind: how everything is connected and the language I use to interact with it.

This new knowledge has also changed my notetaking practices. I’ve started using markdown when taking notes for other classes, utilizing the basic “language” to section off and organize them as I go. I also learned how to add/modify the basic journal script we used in class to create an automatic/pre-formatted outline for my class to fill in as I go. It’s helped me stay organized without the pesky task of repetitively copying & pasting or typing out a new outline every time I want to take notes. I’ve also started using it to draft poems and papers because I can divide different drafts/versions using leveled headers.

Future Ambitions

This new knowledge and understanding has catalyzed my newfound obsession with coding and using Terminal. It’s introduced me to a new subject and set of skills I can learn. I’ve always wondered about the inner workings of computers and what exactly “coding” meant, but had previously relegated it to the collection of “questions I have, but probably won’t understand the answer to.” The things we’ve covered so far have provided me with the basic tools and understandings to start rooting through my computer. It’s also instilled in me the confidence that I’m capable of learning/understanding programming and web development. Now, in my spare time (and sometimes when procrastinating), I’ve started rooting through my computer: I’ve taught myself how to move files more efficiently, how to root out pesky software/apps that I’ve been trying to find and delete forever, and how to override permissions (of course with the help of google).

Another one of my new curiosities/ambitions is to learn about how binary relates to code and the mechanisms/information that enable our computers to work. I also want to know more about writing/modifying the code on (?) my computer to achieve things that aren’t possible (even with the advent of Apple’s new “Shortcut” app), particularly with the multiple keyboards/languages and special characters (the options in system preferences sadly hasn’t given me the power to do what I want). In general, though, I’m interested in learning about/starting the journey to discover the limits of computers (what can and can’t be done? What can I mess with? What can’t I? And why?).