Tag: Georgian Architecture

  • Midpoint Milestone: 6 Months Down, 6 Months to Go

    Midpoint Milestone: 6 Months Down, 6 Months to Go

    Midpoint Milestone (Photo: Geo Davis)
    Midpoint Milestone (Photo: Geo Davis)

    Yesterday was a meaningful midpoint milestone in my quest to post a Rosslyn update every day without fail for an entire year. 

    Six months, 26+ weeks, 184 days. One new installment every 24-hours without fail. Rhapsodizing Rosslyn, celebrating our team’s accomplishments, soapboxing historic rehab and adaptive reuse, showcasing seasonality snapshots and historic Essex memorabilia, weaving in some hyperlocal haiku and place-based poetry, illuminating the mercurial transition / transformation we’re currently navigating, and sharing boathouse and icehouse updates, intriguing artifacts, and wildlife observations. 

    Call it a 184-day streak. Or call it dogged determination. Either way I have 181 days to go until I reach my goal. And with each new post, each small victory, I am growing more and more confident that I will accomplish my mission of 365 posts, one complete year of daily updates beginning on August 1, 2022 and concluding on July 31, 2023. 

    So how to commemorate this midpoint milestone? With 6 months down and 6 months to go, it feels momentous enough to pause and praise my good fortune. But should this benchmark be acknowledged with a celebratory salute? A solemn ceremony? A toast, my first spirited sip after 31 days of teetotaling? (Yesterday marked the conclusion of my 7th or 8th, maybe even my 9th “dry January”.) Or perhaps a decadent dessert after a sugar free month? (For some sadomasochistic reason I’ve decided in recent years to add a sugar fast to alcohol abstention during the month of January, a timely recovery after the excesses of Thanksgiving-through-New Years…) A new month (ie. rabbit-rabbit) ritual transcending the delicious dinner I shared with Jim and Mark two nights ago at Juniper?

    Slow Cooked Whole Rabbit: cumin, blood orange and smoked paprika glazed, corn tortillas, chimichurri, salsa fresca, refried beans (Source: Juniper at Hotel Vermont)

    Maybe a romantic romp with my bride who suggested, upon retrieving me from the airport yesterday, that we celebrate a belated anniversary to compensate for the one we missed this past autumn when she was unwell. 17 years of marriage and 21 years together. I’m incredulous even as I type these numbers. Neither seems remotely possible. But my 50th birthday seemed similarly inaccurate this past spring, and I’m obliged to accept it.

    Or how about we honor the 200th anniversary of Rosslyn’s front façade, ostensibly completed in 1823? (Apparently 3/5 of the building — the two window portion to the north of the entrance, as well as the entrance itself — was completed in 1820. The remaining 2/5, including the two windows to the south of the entrance and comprising the dining room downstairs, a guest bedroom and Susan’s study on the second floor, and another guest bedroom on the third floor, was most likely finished three years later in 1823, fulfilling the the architectural promise of this classic Federal home with Georgian and Greek Revival elements.

    An auspicious confluence of milestones and anniversaries. I’m choosing to interpret this is a good omen even as I nevertheless acknowledge that I’ve meandered from my original mark, hoisting the flag at my halfway point, mid-journey in my post-a-day quest. I recall an earlier waypoint in this quest, an update I published on October 10, 2022 when I was still just shy of halfway to where I am today.

    Yesterday marked ten weeks of old house journaling. Every. Single. Day. Two months and ten days back at the helm of this wayward, meandering, sometimes unruly experiment I call Rosslyn Redux. I emphasize the daily component of this benchmark because it’s been an important part of the goal I committed to at the end of July. (Source: Old House Journaling)

    Then as now my emphasis on everyday journaling remains a top priority.

    Over the last few years, Susan and I have scrutinized our hopes and expectations with Rosslyn. We have reevaluated our plans as they originally were in 2006 when we embarked on this adventure and as those plans evolved during the decade and a half since. It’s been an extended period of introspection, evaluating our current wants and needs, endeavoring to align our future expectations and goals with respect to one another and with respect to Rosslyn, and challenging one another to brainstorm beyond the present.

    There’s no question but that our impromptu quarantine at Rosslyn during the spring and summer of 2021 catalyzed some of this soul-searching. But so too have the many life changes in recent years. Our gradual shift toward Santa Fe as our base and Essex as our getaway rather than the other way around. The loss of Susan’s mother. My parents’ retirement near us in Santa Fe. Our nephews and nieces growing up and expanding their orbits far beyond Rosslyn. A perennially postponed but driving desire to collaborate on a smaller, efficient, creative lakeside home of a different DNA altogether, an unrepressable will to imagine into existence the sort of slow cooked (albeit shapeshifting) and highly experimental homestead we originally envisioned in 2003-5 when we first began to explore our Adirondack Coast homecoming. And there is that hiccup in our 2006 original timeline, our 2-4 year vision for homing at Rosslyn until we’d managed to reboot and reground, until we were ready for our next adventure. Those naive expectations were eclipsed — willingly and joyfully — within the first year or two.

    So what does this have to do with my daily Rosslyn updates?

    Everything.

    In committing to this daily practice last summer I was acknowledging that I had some serious work to do. In order for us to constructively sort through out collective vision for the future, to determine whether we’re too fond of Rosslyn to proceed with plans for designing and building the lakeside retreat we’ve conjured over the years, to honestly assess our willingness and our readiness to hand this sanctuary over to another family, both Susan and I are undertaking the sort of “deep work” that will hopefully enable us to make some decisions. I’m talking about 100% honest, prolonged consideration. Rosslyn has quite literally been a part of our family, and not just our nuclear family. Can we untangle her? Are we willing to let her go? Can we joyfully pass the privilege on to new custodians? Or are we not yet ready?

    For me this daily practice, digging deep into sixteen and a half years of living and loving Rosslyn, is my time and place to work through these questions. To sort it all out. To find peace and confidence in my convictions. And six months in, I believe that I’m on the right path. Not all the time. There have certainly been some tangles and tangents that got away from me before I realized what was happening and reined them in. But the constant conversation — *internal* as I study, reflect, and compose these installments as well as *external* as I share these updates and then interact with many of you — is reinvigorating and reawakening Rosslyn from her comfortable slumber (and me from mine!) 

    So this midpoint milestone is a profoundly significant benchmark for me personally. It’s the tangible representation of my germinating confidence and clarity. It’s the measurable mean between a conflicted outlook and the conviction I’m hoping to discover over the next six months. In a real sense, it’s a halfway point toward the sort of rehabilitation that we’ve been undertaking with Rosslyn’s buildings and grounds since 2006, only in this case the journey is profoundly personal. Instead of historic architectural rehabilitation, it is restoration of my innermost wonder, my romantic dreams, and my idealistic hopes. With passion reawakened and a map forward becoming more apparent each day, I’m tempted to see this benchmark as the sort of celebration enjoyed upon finally reaching a base camp, a lofty peak viewable in the distance foreshadows the ambitious ascent ahead but also offers a majestic affirmation of the reachability and proximity of the summit. Today marks just such a halfway point, an opportunity to appreciate the accomplishments so far, and an incentive to forge ahead.

    Thank you for meeting me in the middle!

  • It’s Not a Bug, It’s a Feature

    It’s Not a Bug, It’s a Feature

    It's Not a Bug, It's a Feature: luna moth (Photo: Geo davis)
    It’s Not a Bug, It’s a Feature: luna moth (Photo: Geo davis)

    Yesterday I made a passing reference to coder jargon when I said that “the bug is beginning to feel like a feature”. (See “Yesteryear or Yesterday?“) I’m not a coder. Never was. Never will be. But I like the way coders think (and sometimes the way they talk.) You may be familiar with the acronym INABIAF or the phrase, “It’s not a bug, it’s a feature“. Its use long ago jumped the software programming border, and today you’ll hear it bandied about in all sorts of curious contexts. Yesterday’s post, for example… 

    An adage too often deployed, too often stretched and distorted, tends to become overly generic. Tends to lose its oomph. I’m guilty, of course. But unrepentant. Chalk it up to poetic license. Or digital graffiti. Or wanton disregard for the sanctity of jargon?!

    Today I’m doubling down. It’s not a bug, it’s a feature. 

    What, you ask, is not a bug? Certainly some of the spunky snapshots I’ve included in this post are bugs. And insects, though I forget what delineates the two.

    When a Bug is Not a Bug

    So many transfixing bugs at Rosslyn, and so little call for their vibrant mugs. Today I change that.

    But what do these fetching flyers have to do with wonky tech talk? I’m working on that. First let’s detour a moment for more versed expertise on the aforementioned phrase.

    WE’LL NEVER KNOW who said it first, nor whether the coiner spoke sheepishly or proudly, angrily or slyly. As is often the case with offhand remarks that turn into maxims, the origin of It’s not a bug, it’s a feature is murky. What we do know is that the expression has been popular among programmers for a long time… (Source:WIRED)

    This article by Nicholas Carr (@roughtype) handily takes up the INABIAF backstory including a bridge deeper into software speak. 

    A standard joke is that a bug can be turned into a feature simply by documenting it (then theoretically no one can complain about it because it’s in the manual), or even by simply declaring it to be good. “That’s not a bug, that’s a feature!” is a common catchphrase. (Source:The Jargon File)

    More insightful, I think, is the embrace (or at least tolerance of) ambiguity.

    It’s not a bug, it’s a feature is an acknowledgment, half comic, half tragic, of the ambiguity that has always haunted computer programming. (Source:WIRED)

    Of course this flies in the face of the stereotypical assertion and aspiration of most coders who express a quasi cultish obsession with purity and absolutes and confidence in the incorruptible virtue of science. 

    In the popular imagination, apps and other programs are “algorithms,” sequences of clear-cut instructions that march forward with the precision of a drill sergeant. But while software may be logical, it’s rarely pristine. A program is a social artifact. It emerges through negotiation and compromise, a product of subjective judgments and shifting assumptions… (Source:WIRED)

    This. From ambiguity to social artifact. Indeed. Pristine aspirations achieve by people-powered processes and resulting in people-powered products. The blurring of reality and circumstance, the possible filtered through the inevitable. Subjectivity and uncertainty and inexactness.

    It's Not a Bug, It's a Feature: rosy maple moth (Photo: Geo davis)
    It’s Not a Bug, It’s a Feature: rosy maple moth (Photo: Geo davis)

    Of Bugs & Ambiguity 

    Yesterday’s bug reference was a lightheartedly dismissive counter to concerns (anticipated but not advanced) about the ambiguity of unreliable, shapeshifting time in my Rosslyn deep dig. While pouring over a decade and a half of detritus that has accrued during our custodianship of this beguiling property I’ve witnessed time’s tendency to blur and become elastic. Memories and even events themselves can become unmoored from their chronological anchors.

    And I was subtly resurfacing an even larger consideration of time and timelessness across the span of Rosslyn’s two centuries. In the case of the capriciously altered boathouse images — a blurred, patinated, age and wear accelerated photograph of relatively contemporaneous provenance — one’s first impression might be to judge the artifact as a time capsule. A voyeuristic glimpse into an earlier time on Rosslyn’s waterfront. Scrolling down through the three images might dissolve the ambiguity despite the absence of dates.

    While grappling with our Rosslyn adventure, I’m struck not only by the ambiguity of time but also of memories and perspectives and opinions. On the one hand, there’s disagreement among the cognoscenti about Rosslyn’s architectural lineage. Colonial, Greek Revival, Federal, Georgian, or an amalgam of two of more architectural periods or styles? On the other hand, Susan and my memories about notable chapters in our own Rosslyn record frequently diverge. Countless conflicting recollections surface in our conversations. When certain things happened. Why they happened. If they happened at all!

    It's Not a Bug, It's a Feature: bumblebee (Photo: Geo davis)
    It’s Not a Bug, It’s a Feature: bumblebee (Photo: Geo davis)

    It’s Not a Bug, It’s a Feature

    I’ve meditated on wavy glass window panes provoking perspective shifts and even paradigm adjustments. I see these flowing lenses as inviting insight as well as intoxication, delivering discernment as often as distortion. And what to make of the potent clarity of art and poetry that can sometimes better translate what facts and artifacts, expertise and authority overlook? Watercolors, for example, can reveal truth more lucidly than photographs. Hand renderings can articulate architecture’s poignance and prowess better than AutoCAD.

    Carr’s conclusion invites us to wonder wider about the possible merits of buggy artifacts.

    The programmer’s “common catchphrase” has itself become a bug, so trite that it cheapens everything it touches. But scrub away the tarnish of overuse and you’ll discover a truth that’s been there the whole time. What is evolution but a process by which glitches in genetic code come to be revealed as prized biological functions? Each of us is an accumulation of bugs that turned out to be features, a walking embodiment of INABIAF. (Source:WIRED)

    And that, friend, is a piece of the puzzle that’s been captivating me for months. My information gathering and analysis and synthesis are rigorous but glitchy. For a long time I aspired to purity, to algorithmic precision. But often yesteryear and yesterday have bled into one another. Often juxtaposed memories mingle and morph, contradictions converge, and dissonance dithers then dissolves. Fragments reveal what we may have missed in the moment. Curiosity and creativity have emerged from the years of quiescence. I’m less and less called to chronicle the past, to husband our history, Rosslyn’s history into some sort of encyclopedic epic. I find myself more and more compelled to reassemble the fragments with an eye to where I am headed rather than where I’ve been. I’m reveling in the playful possibility of reimagining and repurposing these ingredients into a sculptural collage; no, a three-dimensional poem; no, a montage-mobile almost imperceptibly gyrating in the rhythmic breathing of a slowly awakening breeze; no, a lakeside sanctuary braided out of found fragments, aromatic melodies, spring starts, and autumn harvest; no,… A buffet of indecision!

    Back to bugs. I offer you three flying features: a luna moth (Actias luna), a rosy maple moth (Dryocampa rubicunda), and a bumblebee. Perhaps, for now, these will suffice.