Architecture is predicting the future

When an architect is asked to design something, part of the challenge is to anticipate the effect that this usually large built and immovable object will have on the many people that will see, use and possibly inhabit it.

Conceptual art approaches can help, for example making a building evoke an idea, or using an idea to start a design, but they are never enough. That my building is 1776 feet high may help get sponsorship, but in it will hardly be perceived.

Fame or notoriety help. Celebrity architects draw buzz and crowds. One can invest genius in a built object and the aura of the famous designer creates a culture around the space.

The inescapable challenge of architecture however is to be present in time and space in a significant way.

Here is an example of how things can go wrong:

In my little town, the well-meaning heritage preservation committee got involved in the review of a design for a pump house that would sit along the waterfront. The building would need to have the volume of a large two storey house.

The committee looked around "for context" and found a nearby older shed that had two stone gable ends and a very symmetrical sloped roof, a kind of 19th century shed. So they strongly suggested that the utility's architect (or most likely engineer), take the cue.

The intention was to reflect the heritage of the industrial waterfront area.

The result was a large, white stucco covered imitation of an old shed, like an over sized paper model of it, sitting there contrasting against the dark water and sky.

I don't think that was the intention. I also think that any architect would have easily anticipated this and informed the client of the danger. Unfortunately, the heritage preservation committee is wedded to form and mimesis (a pompous architect term meaning copycatting). Unfortunately, it is an easy notion to sell, a concept that seems to make sense, reflect shapes, and if you are lucky materials.

An aside:
I agree with many of my colleagues who say that if you are going to do some restoration work or add to an older building, choose one: re-use material or re-use form and proportion, but don't do both, at the risk of getting some half-assed mimesis.

Ok, so back to the story. This thing now sits on the waterfront, annoying, out of place, and a reminder of industrial sheds we lost, but bigger and worse.

So instead of learning a lesson, this heritage committee moves on, job well done, and is now addressing the problem of our train station. Again, mimesis is being suggested, but this time there is no proximate context, so they looked in the pattern books for old train stations with huge eaves, and came up with some hybrid Frank Lloyd Wrightish stone bunker, because they wanted the stone of course.

What is galling is that the railway people had proposed a very nice, airy design, with proper functional overhangs to protect people on the platform, but with nice glass, and curves and a good light feel to it, considering the barren context of the area, a jewel that may have lightened the oppression of the district.

I don't think it will be realized, because no-one thinks that architects can predict the future, especially when the heritage preservation committee is locked in the past.

A Tale of Two Realities

I have just begun a new job. No hiatus between this new one and the old. One day I am in hell, the next in paradise.

The one I left was as a software manager in a large organization, and the current one is as a software lead in a very small organization.

Other objective differences: the previous job was bureaucratic, there were many processes and constraints and a network of communication and decision paths, and the systems my team built had to reflect the complex interrelated and often historically constrained requirements.

The current one is technical, working within a small team and with very precise mostly self-defined scientific requirements, adjusted to meet specific customer requests. The software has to run precision equipment to capture and calculate results within extremely tight tolerances, both in time and numerical accuracy. The only measure of quality is repeatable precision. The culture is one of technology and science.

In the new job, I report to people who have the same engineering training as I do, who have more experience in the R&D business than I do, who I can ask questions of without risk of offending or destabilizing them emotionally. Peers and superiors in all senses.

In my previous job, I reported to people who asked me to explain what I did "in simple terms" and who liked to hear themselves talk so that they could pretend to make sense of their lumbering thoughts in public forums, often referred to as "meetings" but which felt like beatings. Dissent could be career limiting.

The analogy I would like to give to dispel any conclusion that I may be a pretentious ass is as follows:

Suppose you are a medical practitioner, a physician, and you see patients in a clinical context. You have to diagnose and prescribe treatment as part of your day to day routine.

Also, suppose that you are "managed" by someone who had not undergone the same level of training as you, say a registered nurse, who knew the lingo, understood the context, but did not feel confident enough to make life or death decisions affecting patient health, but felt competent enough or was somehow appointed to tell you, the physician, how to run your practice.

For example, "please use language that is easier to understand in your charts". Or  "make sure your handwriting is legible for the pharmacist", or " you have not seen your quota of patients today, why did you spend 6 minutes more than average with Mrs. Smith today?".

Could you practice under such circumstances? How long would you last?

I lasted 5 years in the analogous IT context. My manager was a technologist, previously a school teacher who joined th IT boom of the nineties and hung on. She did a bit of COBOL programming, hated it and went into management because she could talk better than she could listen or understand.

She is proud to claim that she does not understand the need for system architecture versus program design, her eyes glaze over when there is talk of latency, language choice, servers, data flow analysis, code profiling, and factoring and she had no patience for options analysis or proof-of-concepts. She will not deign to read code. She has trouble with email client software and spreadsheets.

She wants simple, clear explanations and plans, and wants to set deadlines before beginning design, because iterative work can only lead to grief. She always used waterfall approaches in COBOL, and they worked fine for her.

Her weakness and fear prevent her from adding value, from making decisions. She was a pass-through for her manager's decisions to me and my peers. No value added, but lots of aggravation and delay. Never understood or wanted the concept of situational management, which is probably the most effective way of managing people, so effective that there have been lawsuits about who has a right to claim authorship and teach it. She is a scared rabbit, hanging on until she can retire and cash in.

Others in that environment have said that we, the technical folk who did the work, should not "speak Neanderthal" when in the presence of senior executives, by which it was meant that we should use non-IT terms of less than 3 syllables. The executives in question were the CIO and her direct reports.

But all this is now in my past, one-day-old stuff. I am now in another world, where the conversations around me centre on measurement tolerances, ADC resolutions, real-time interrupt-driven code, clock speed and sampling rates, hierarchical state machine approaches, language selection and compiler efficiencies. I have scope probes and micro-controllers on benches beside me, no fuzzy walled grey cubicle partitions in sight, and a project to deliver with people I can talk to who want me to talk dirty.

I am in heaven.