A paper idea I initially started developing in 2014 and recently retooled for a coastal context...Read More
In this current Age of Information, those of us who are not “digital natives” tend to look back on the days we were first introduced to personal computers and wax philosophical about how the simple integration of a certain digital technology has so quickly and so profoundly transformed our culture and commerce, as well as whether such transformations are bringing our society in the right direction. The Alphabet and The Algorithm is an architect’s version of that rumination. In it the reader is introduced to the authorial voice of Mario Carpo—an architectural historian and critic who also serves as professor of theory at University College, London—and then taken on a tour through the story of authorship in architecture and how revolutions in methods and technology have spurred its evolution. In its simplest form, Carpo’s main argument is that architecture has changed from an art of craftsmanship and on-site collaboration, where no work would ever have one true author; to one of notation and identicality between plans and actual constructions, thus solidifying the architect’s role as sole designer; and now to an act of digital differentiation and mass customization, which has the charm of individual craftsmanship while retaining a new authorship role for the architect.
While there is no doubt that The Alphabet and The Algorithm makes an important argument in the realm of architectural design—especially given the nature of our current design dialectic—it also opens an opportunity to discuss the subject matter from the perspective of landscape design. In this paper, I hope to provide a starting point for that discussion by highlighting the ways Carpo’s collated history has similar relevance in landscape architecture, the ways in which it differs, and finally, the way landscape fits into the future the author predicts for the design professions.
Architecture and landscape design share many similarities in their histories. This makes sense since projects in the built environment have almost always required services from both disciplines—not to mention the many instances in history where the roles of architect and landscape architect were filled by the same person. While the knowledge of these similarities is well documented as it pertains to styles, movements, and people, Carpo’s historical summary offers an exceptional dialogue which deals with tools and authorship. I find the most striking observations to be those on the recent emergence of cad-cam, 3-d design, and fabrication.
Just as the industrial revolution pushed architects to provide economies of scale in both design production and construction, so too did it push landscape architects to manufacture replicas of designed landscapes in inappropriate places and at inappropriate scales, all in the name of cost saving. But as Carpo points out, “In a digital production process, standardization is no longer a money-saver. Likewise, customization is no longer a money-waster.” [i] Thus, landscape designers now have the freedom to focus their time on deciphering the parameters of the landscape instead of preoccupying themselves over the parameters of production costs.
Another similarity the landscape profession shares with Carpo’s futuristic architects is the advantages afforded by three-dimensional design software. As he puts it “even though a computer screen is two-dimensional, all three-dimensional forms visualized through it may exist in a computational three-dimensional space right from the start,” [ii] thus saving time and brain damage in translating renderings into notational documents. Furthermore, Carpo expounds on the idea that this narrative of shared digital efficiencies in the architectural and landscape design fields is also evolving into one of shared innovation:
“due to cad-cam integration, and counter to the Albertian principle of separation between notation and construction, digital architects today are increasingly designing and making at the same time. Acting almost like prosthetic extensions of the hands of the artisan, digital design and fabrication tools are creating a curiously high-tech analog of preindustrial artisanal practices. . . . Owing to cad-cam integration and bim (building information modeling) software, design and production will increasingly merge and overlap in a single, seamless process of creation and production. In some cases, limited for now to the fabrication of small objects and prototyping, existing cad-cam technologies have already achieved that stage: an architect’s design can be immediately and automatically fabricated—if need be, in front of the architect and while the architect is still working on it.”[iii]
While the Alphabet and the Algorithm illustrates a great deal of similarity in the histories of architectural and landscape design, there are a number of striking differences that are important to mention, the most notable one being the notion of the author in landscape design. Throughout most of the work Carpo repeatedly emphasizes the rise of Alberti as one of the most pivotal points of architectural history, mainly because of the self-assertion of the architect as sole designer through the use of notational drawing. This is done so by first distinguishing the designer from the craftsman by requiring that the finished work be an exact replica of the scaled plan drawing. As Carpo states “in the Albertian, allographic way of building the only work truly made by the author is the design of the building—not the building itself, which by definition is made by others. The only way for Alberti to claim an extension of authorship, so to speak, from the drawing to the building was to require that the building and its design should be seen as perfectly identical.”[iv] With this reformed structure of designing and building “architecture ideally acquires a fully authorial, allographic, notational status. Insofar as a building and its design are considered notationally identical, one can identify an architectural work either with the design of the building or with the building itself,” or in other words “the design of a building is the original, and the building is its copy.” [v] This argument for notation and identicality defining authorship, while strong in the case of architecture, loses clout in the realm of landscape design. This is because 1) landscape design deals with the natural environment which is impossible to represent with exactness, and 2) landscape design is inherently more collaborative than architecture—mostly due to the aforementioned problem of drawing and building changes in nature—and therefore defines authorship differently.
Because landscape designers work with the natural environment, the way that they utilize the Albertian method of design has its limits. While certain notational tools (such as a scale or dimensions of structures/materials) can be used with a sense of identicality, they can never apply to the entirety of a site design and can subsequently never claim sole authorship for the designer—i.e. one cannot look at a tree in Central Park, identify its exact structure and placement within the original plan, and then award sole authorship of the tree’s design to Frederick Law Olmsted. This is because the tree is a living and changing part of a greater living and changing system. Thus, it is impossible to notate and replicate its design with precision.
Historically, this lack of notational precision has necessitated that designers be collaborating with craftsmen, builders, and planters through the entirety of design and construction, if not preforming the work themselves. Therefore, when the work is done, the designers claim to authorship comes not just from the ability to produce a plan that builders can replicate with some precision, but also being able to address, in person, the inevitable visual discrepancies of that plan. So, we see that the authorship of a landscape architect is in most cases functionally different from that of an architect, at least in the Albertian sense of the word.
LANDSCAPE ARCHITECTS AND THE FUTURE OF DESIGN
With the fall of Albertian design methods and the rise of digital software tools with their differential customization, the nature of the designer’s authorship is changing dramatically. Carpo notes that this is particularly unsettling for architects, saying that with “the sometimes messianic, sometimes apocalyptic premonitions of a digitally induced disappearance of traditional authorship, architects have additional reasons to fear developments that may amplify the role of other participants in the design process.”[vi] I think he is right, and would even go as far as to add that, in contrast, landscape architects have additional reasons to be excited about the very same developments, because their skill sets are tailored for the new age of design.
To quell the fears of how architects will define their authorship, Carpo ends his work by asserting that such definition will come in building algorithms and functions in the latest digital software. He says, “today’s stilus is not the style of the designer but the inevitable trace left by the software being used— which, just as Cicero’s stilus was, is itself man-made and produced by specialized technicians.”[vii] Still, though, he even qualifies his words when he states that as we enter a new realm driven by “exactly repeatable, visible imprints,” one must be wary that “the erratic drift of manual copies may distort or confuse the sign of the original archetype and, as a result, conceal the identity of its author, or make it irrelevant…”[viii] In the case of the landscape architect, there is no need to fear such things because our authorship is not defined in the same way. First and foremost, we care that landscapes function and that people thrive in them, and we ensure that such happens by tailoring our design process to the problem at hand. Our authorship is in our process rather than our product, though there will undoubtedly be stylistic cues in the latter.
As Carpo continues to discuss the way new tech is changing design, it becomes evident to me that the way in which landscape designers see these tools is often different than that of the author. Perhaps the most clear example of this is the claim that “digital technologies for design and fabrication may…still be seen as instrumental mediators, but functionally they are more akin to material utensils, like hammers and chisels, than to traditional notational vectors such as blueprints or construction drawings,” and moreover that “Cad-cam applications are responsive tools for designing and making at the same time, not recording tools for scripting a final but inert set of design instructions.”[ix] Against Carpo’s wishes, landscape architects are most often using them in exactly that way, using them to digitize hand sketches, draft construction documents, and create digital renderings rather than iterate the actual design. There is good reason for this. In the author’s ideal world, the new school designer is fluent enough in new technologies to wield them in the same way the old schoolers used pens, trash paper, and models to iterate. While it is a nice idea, it is simply not a reality of the times. Most designers are not well versed enough in these newer design tools to use them for iterative purposes, nor are the technologies advanced enough to iterate at their level of expertise, or in some cases abstractness—remember, as the book states, even Frank Gehry still starts his designs with sketching and paper models.[x] That is because those sketches and paper models are Gehry’s strongest way of communicating his ideas.
I think Carpo is aware of this. He says that “in the most extreme cases, when a form is too difficult to notate geometrically, the last resort of the designer may well be to abandon the modern design process altogether, and return to the traditional, pre-Albertian, autographic way of building. If you can’t draw what you have in mind in order to have others make it for you, you can still try to make it yourself.”[xi] Even though he is speaking of notational methods in this quote, it also applies to the 3-d design methods he champions, at least in their current state.
This is changing, however. With each new available software update comes a new level of sophistication in design capabilities. As Carpo aptly states, “digital tools no longer need to separate the thinker and the making; on the contrary, if pertinently put to use, digital technologies may reunite most of what mechanical technologies had alienated—including the various communities that in the pre-mechanical world were associated with, and dignified, all Things handmade.”[xii]
This new reality of differential mass customization is not only changing the process for designers but also the stakeholders. With digital ubiquity on our doorstep the public can now be a part of the input phases like never before, and “the participatory nature of the design process…is equally evocative of the collective and often anonymous way of building that was common on medieval building sites before the humanists’ revolution…the contemporary digital technologies are in many ways closer to some cultural technologies that preceded the mechanical age than they are to the mechanical age we are now abandoning.”[xiii] But with this opportunity there comes the enormous challenge of influencing the public to become adept to both the technologies and the design process. There is a big difference in knowledge base between the anonymous builders of medieval times and those of today, namely that the former literally knew how to build things and therefore understood the functions and implications of a design decision. This understanding is not so universally found in the latter group. While the current generation knows more than any other about the types of things that can be built because of our shear exposure to information in the abstract, the segment of our society that understands where the rubber meets the road in practice is noticeably smaller than those before us. If we are to embrace the new world of “seamless, on-demand customization through interactive decision-making, hence—ideally—social responsibility in design, as well as parsimony in the use of natural and human resources,”[xiv] we have to have a public that is educated enough to know what such things look like. It will not happen incidentally.
The transition to digital design technologies is inevitable; the benefits and demands far outweigh any perceived costs. The way we transition, however, is not. I believe Carpo is right about what the future holds for design, but until the day we can all use software as naturally as we use pencil, paper, or clay, we must be prudent in the role we let such software play in our process. Flashy new toys may augment the way we play, but they will never replace the imaginations that inspire us to play in the first place.
[i] Carpo, Mario. The alphabet and the algorithm. n.p.: Cambridge, Mass.: MIT Press, 2011. Louisiana State University, EBSCOhost (accessed September 5, 2017), 41.
[ii] Ibid. 33
[iii] Ibid. 45, 79
[iv] Ibid. 22
[v] Ibid. 26
[vi] Ibid. 115-116
[vii] Ibid. 100
[viii] Ibid. 100-101
[ix] Ibid. 35
[x] Ibid. 38
[xi] Ibid. 32
[xii] Ibid. 119
[xiii] Ibid. 118
[xiv] Ibid. 126-127
This past summer, I became a Mormon-Catholic New Urbanist, and I did it all without putting on a nametag, going through a catechesis, or getting a degree from the University of Miami! How, you say? Allow me to explain:
From the end of May to beginning of August, I worked as a Planning Intern at the Salt Lake City office of Michael Baker International, a multidisciplinary engineering firm that houses an Urban Design Studio. Since the SLC office has only recently added a planning branch, I was essentially helping the director—who is, comically enough, also named Michael, and has a senior executive supervisor named Michael—to build a program and reputation from the ground up. To say I learned a lot would be an understatement of epic proportions. I was able to practice my graphic software skills daily, understand the nuances of the RFP and marketing process, schmooze with potential clients who are big name developers, get a sense of the culture in an engineering office, learn new ways of implementing design concepts in land use and entitlement packages, and learn about new programs, to name a few. But I think it is safe to say the most interesting thing I was able to do this summer was get into the mind of a supervisor/mentor who is a bona fide New Urbanist, committed to his principles, and is innovating within his paradigm.
When I say bona fide, I mean bona fide! So much so that when Mike was pursuing his Master of City and Environmental Planning at Arizona State University and saw that he didn’t have any teachers who knew or were willing to teach him about New Urbanism, he invented his own curriculum and then later taught the classes himself to undergrads. So much so that he is a CNU Chapter officer and has headed up a CNU conference. So much so that he will shout it from the rooftops in a toga if provoked. Okay, maybe not to that extent, but is it clear enough that he is a real New Urbanist and not just someone who vaguely likes the ideas? It’s a rare thing these days to meet someone so deeply committed to a design movement—I feel that, at least for the moment, the days of manifestos, charters, and theorists actually giving themselves labels are becoming a thing of the past, since my generation seems very averse to the idea of ‘being put in a box’—so I thought I should take advantage of that and really let him take me on a journey through the Smart Growth approach.
Here is where the Mormon-Catholic thing comes in. While there are some very well defined principles of New Urbanism in the CNU Charter, there are other places in which the actual practice of New Urbanism is left up for interpretation, and can therefore be seen as not sophisticated enough for local circumstances. Ironically, the people who point this out the most are often the New Urbanists themselves. No one is more aware of the need to update and calibrate things like the Smart Code than those who crafted it in the first place (which, as a side note, I think this fact is often overlooked by the critics of the movement). Mike’s response to this need is something he calls the Community Development Code or CDC, which is the project I worked the most on throughout the summer.
Here is my quick and dirty synopsis of the CDC:
What is it?
The CDC is a zoning and entitlement code for building strong communities that are true to their local character. It sets context by looking to historical land use patterns of the region and municipality in question, organizes its development using an advanced version of the transect, and frames the submittals process around the concept of subsidiarity.
- Historical Land Use Patterns
- In the case of Utah, the precedent is set by the Plat of Zion, a concept for Mormon community building envisioned by Joseph Smith and implemented by Brigham Young in over 500 communities of ranging size throughout the Mountain West
- Advanced Version of Transect
- Instead of simply using the T1 to T6 designations from the Transect, the CDC looks to define land use context by establishing development areas, community types, block types, and lot types which vary in character and intensity according to local conditions.
- Development Areas map neighborhoods, infrastructure, sensitive lands, etc
- 9 Community Types that vary in population and character
- 6 Block Types that vary in intensity and form
- 9 Lot Types that vary in intensity and form
- Subsidiarity (based on the governance of the Catholic Church)
- Submittals process attempts to push decisions down to the most local competence level as possible. This is to give developers more time and flexibility in their decision making—so that they may build incrementally in response to the market—while retaining the certainty that cities require.
Why did it come about?
While Mike Hathorne was making plans for a number of communities in Utah, he noticed some areas where the New Urbanist Smart Code was falling short in calibrating plans specific to the needs of cities along the Wasatch Front. While there were certain universal principles that were helpful in crafting zoning legislation based on the rural-urban transect, there were also areas where the transect was just too broad for New Urbanist lay people to tailor to the nuance in their cities’ circumstances. Some of these areas include developer-city relationships in decision making/submittals, scalability of the transect at the community, block, and lot levels to fit context, and adding density without diminishing neighborhood character.
How is it implemented?
The code can be delivered in a number of ways, some of the more common being as a land use chapter in existing legislation (usually for specific districts where cities want to “try it out”), as part of a new development (such as a PUD), or as a rewrite or overhaul of the entire zoning code.
Where can it be implemented?
While the prototype of the code has been crafted to work in the context of Utah communities, it is built for flexibility and can be calibrated to just about any community in the U.S.
Who is it meant for?
It is the hope that state, regional, and local governments could use the code to craft their legislation; but it should also be emphasized that one of the code’s strongest aspects is its ability to be used by developers to gain more flexibility for (best practice) innovation in their place making.
So now that you know a little about the work, the question is so what? What are the biggest takeaways from this experience with the CDC and working at Michael Baker this summer? I would point out three:
- As designers, we really need to understand the policy implications of what we do, especially as it pertains to good community planning,
- Things like the CDC can be invaluable to communities that need to shape up their development practices but want to keep the character of their neighborhoods, of which there are many in Louisiana, and
- If we are to tackle the biggest problems facing our infrastructure and environment today, we must accept the reality that it behooves us to work across disciplines if we are to come up with cohesive solutions.
If you are interested in learning more about the code, I strongly encourage you to drop Mike a line. You won't regret hearing more about the code from the mouth of its author.
Welcome to Thoughts on the Boards!
If you've made it here, it's probably because you either saw that I decommissioned my social media accounts and followed the link from the old instagram out of curiosity (please forgive me if you're underwhelmed), you followed the link from my portfolio to see if I am employable (please say yes), or you found this page by accident (please let me know how in the world you did it). No matter how you got here, I think you deserve an explanation as to why I started this website and why I wanted to include this blog in the mix.
When I started design school last fall, it felt as if I was coming upon a watershed moment in my relationship with the arts. After years and years of musical performance, songwriting, poetry dabbling, and (very) amateur filmmaking--all the while wishing I could dedicate time to learn visual media--here I was in the first semester of a Master of Landscape Architecture degree, drawing with charcoal, sculpting clay, glueing together photo collages, laser cut modeling, sketching the LSU Quad, living the dream. I had finally found a profession where I could express my creativity in a focused and sustainable way. Instead of living paycheck to paycheck on the fumes of my bouts of inspiration, I could let the inspiration come to me on the coattails of each new client and each new site specific design problem. Not to mention the fact that my new skill set will allow me to do even more art for personal purposes when those bouts do come. What a deal!
The first semester passed, then another, and I quickly found myself staring at a mountainous backlog portfolio updates and ideas for personal projects. At the same time, I had been reading about Cal Newport's views on social media in his book Deep Work, and had been feeling a need to drastically change my use habits. I really identified with his style of time management that focuses on what he calls deep work, or "the ability to focus without distraction on a cognitively demanding task...a skill that allows you to quickly master complicated information and produce better results in less time," and really wanted to experiment with his formula for mastering it; according to Newport, this required cutting out or drastically reducing social media use. In his words, “this strategy picks specifically on social media because among the different network tools that can claim your time and attention, these services, if used without limit, can be particularly devastating to your quest to work deeper. They offer personalized information arriving on an unpredictable intermittent schedule – making them massively addictive and therefore capable of severely damaging your attempts to schedule and succeed with any act of concentration.” (205) This is a tall order, as most of us who have used social media know; these powerful platforms have been specifically engineered to give us perpetual FOMO for not using them, thus creating a feedback loop of shallow work that deprives many knowledge workers of the chance to work on something meaningful for their personal and professional progress.
The key to making the weaning process smoother, Newport suggests, is structure. “Without structure," he writes, "it’s easy to allow your time to devolve into the shallow – email, social media, web surfing. This type of shallow behavior, though satisfying in the moment, is not conducive to creativity. With structure, on the other hand, you can ensure that you regularly schedule blocks to grapple with a new idea, or work deeply on something challenging, or brainstorm for a fixed period – the type of commitment more likely to instigate innovation.” (227) This site is one of my tools for establishing that structure.
Things to Keep in Mind About This Website
- I only have two goals for this site: Consolidation and Documentation
- Consolidation: The idea is that if I consolidate my online presence into a single platform, I can create a sort of one-stop shop where I can house an extension of my portfolio and provide a place where friends and followers can see what personal projects I'm working on, what new music I'm writing, or read general insights at any given time (hence the name Thoughts on the Boards). This also helps me to manage my time more efficiently (now I have only have to schedule a block of internet time for updating things on one website instead of 5 or 6) and meaningfully (the only shallow activities I will allow myself to be doing will involve either communicating the progress of my deep work endeavors, searching for employment, or showcasing personally engaging projects, thus reducing my internet usage and making the time I do spend on it more focused and fulfilling).
- Documentation: While each project page in itself will have a level of editing or curation to it, the collection of works together will probably not read that way. This site is not the site of an artist, or an academic, or a designer, or a writer, or a musician, or a filmmaker, but a generalist trying to nourish his creativity and keep himself accountable through documentation.
- Blog posts will be on a slew of topics; life, love, design, politics, religion, art, literature, movies, culture, travel, and food are all fair game. All writing styles are also fair game, so the line between formal academic essays, poetry, and stream of consciousness will be very fine. The posts are not meant for anyone in particular to respond to them, but I welcome the dialogue!
- I don't sell things here, and I don't plan to.
- I only give the website link to potential employers when asked. It is not meant to act as a replacement for my portfolio nor as a self-promoting design website.
In short, I created a website, it has a blog, and I hope you enjoy any interactions you might have with it!