Hans de Zwart: Technology as a Solution…

A techno believer's path in learning…

Archive for June 2010

Christopher Alexander’s “A Pattern Language”

with 10 comments

A Pattern Language

A Pattern Language

I have just finished reading Christopher Alexander‘s A Pattern Language: Towns – Buildings – Construction, one of the most wonderful books I have read in years.

The scope of the book is incredible. It sets out, in plain terms, to empower people to design, build and shape their own surroundings. It does this by creating a “pattern language”, a kind of generative grammar with 253 patterns that can be used to make things. The patterns move from big town scale patterns (e.g. The Distribution of Towns, Magic of the City, Web of Shopping, Nine per Cent Parking), via medium building scale patterns (e.g. Wings of Light, Intimacy Gradient, Staircase as a Stage) to small  construction scale patterns (e.g. Structure follows Social Spaces, Low Sill, Filtered Light, Different Chairs).

Each pattern is described in a similar way: there is a picture showing an archetypal example of the pattern, then a paragraph describing the context of the pattern (in which larger patterns does this pattern fit), next in bold a headline giving the essence of the problem, then a research based exploration of the problem, next in bold the solution stated as an instruction, then a diagram as a visual way of describing the solution and finally a paragraph describing which smaller patterns can help this pattern. Each pattern also comes with a label signifying how sure the authors are that this truly is an universal pattern.

The breadth of topics in the book is baffling (it took the authors about seven years to research and write it). Let me just give you some random quotes to show you what I mean (doing the book a gross injustice by leaving out a lot of context).

On the magic of a cities:

The magic of a great city comes from the enormous specialization of human effort there. Only a city such as New York can support a restaurant where you can eat chocolate-covered ants, or buy three-hundred-year-old books of poems, or find a Caribbean steel band playing with American Folk singers.

On the evils of supermarkets:

It is true that the large supermarkets do have a great variety of foods. But this “variety” is still centrally purchased, centrally warehoused, and still has the staleness of mass merchandise. In addition, there is no human contact left, only rows of shelves and then a harried encounter with the check-out man who takes your money.

On grave sites:

No people who turn their backs on death can be alive. The presence of the dead among the living will be a daily fact in any society which encourages its people to live.

On why buildings should have gradients of intimacy:

When there is a gradient of this kind, people can give each encounter different shades of meaning, by choosing its position on the gradient very carefully. In a building which has its rooms so interlaced that there is no clearly defined gradient of intimacy, it is not possible to choose the spot for any particular encounter so carefully; and it is therefore impossible to give the encounter this dimension of added meaning by the choice of space. This homogeneity of space, where every room has a similar degree of intimacy, rubs out all possible subtlety of social interaction in the building.

On why your windows should have relatively small panes:

[Thomas Markus] points out that small and narrow windows afford different views from different positions in the room, while the view tends to be the same through large windows or horizontal ones. We believe that the same thing, almost exactly, happens within the window frame itself. [..] The view becomes alive because the small panes make it so.

On lighting every room from two sides:

When they have a choice, people will always gravitate to those rooms which have light on two sides, and leave the rooms which are lit only from one side unused and empty.
This pattern, perhaps more than any other single pattern determines the success or failure of a room. The arrangement of daylight in a room, and the presence of windows on two sided, is fundamental. If you build a room with light on one side only, you can be almost certain that you are wasting your money.

On modern impersonal interior design:

Do not be tricked into believing that modern decor must be slick or psychedelic or “natural” or “modern art,” or “plants” or anything else that current taste-makers claim. It is most beautiful when it comes straight from your life – the things you care for, the things that tell your story.

On high buildings (imposing a four story limit):

There is abundant evidence to show that high building make people crazy.
High buildings have no genuine advantages, except in speculative gains for banks and land owners. They are not cheaper, they do not help create open space, they destroy the townscape, they destroy social life, they promote crime, they make life difficult for children, they are expensive to maintain, they wreck the open spaces near them, and they damage light and air and view. But quite apart from all this, which shows that they aren’t very sensible, empirical evidence shows that they can actually damage people’s minds and feelings.

I could go on and on…

Written in 1977 it is clear that this is a very “seventies” book. The belief in what we in The Netherlands would call “De maakbaarheid van de samenleving” (the ability to create/design/mold society) is very high. It was interesting to reflect on where I grew up and how much of that place was designed according to the same kind of thinking and ideals. I could also find many of seventies based educational philosophy of the school I used to work at in the book. The open doors, the integration of inside and outside, there are even some very explicit ideas on education and learning in the book.

Although many of the patterns are probably very universal (they are very human), I do think the book has some strong cultural biases. This doesn’t make it less valuable though.

The book has really made me want to scratch my own creator’s itch. It makes you want to design things. (Apparently Will Wright, the creator of SimCity, wanted to create this game after reading the book).

What I want to create, inspired by this book, is not a town or a house. I want to write a new pattern language. Wouldn’t it be great if we had a generative grammar for technology enhanced education (or using another term, online learning events)? I see that there have been some attempts to do this already (here and here), but I would love to create a much more extensive work that is in the style of Alexander. Is there anybody who would like to help me? Shall I start a wiki?

If you want more information about the book, then go to its website or read hyperlinked summaries of all patterns.

Written by Hans de Zwart

15-06-2010 at 22:16

ReWork Rehashed

with one comment

Arjen Vrielink and I write a monthly series titled: Parallax. We both agree on a title for the post and on some other arbitrary restrictions to induce our creative process. For this post we agreed to write about the 37signals book Rework. Each of us will write about the three things in the book that we already do, about three things we will do from now on going forward and about three things that we wish our employers would do from now on. You can read Arjen’s post with the same title here.

Rework

Rework

Jason Fried and David Heinemeier Hansson of 37signals and Ruby on Rails fame have just written a new book titled: Rework (you can download a free PDF excerpt). Reading it gave me an ambivalent feeling: these authors are obviously very good in what they do and they have managed to build a successful business monetizing different parts of their talents, but the book feels like a monetization effort too and the number of words per Euro are very low. Arjen Vrielink has written a quite damning review on Goodreads.

Nonetheless it has some interesting lessons to offer. It has about 100 pieces of advice for people starting their own business or working in a business. Some of the advice I already practice, some advice I will try to practice from now on and I wish that the company I work for would practice some of the advice going forward.

Three chapters about things I already do:

Build an audience (page 170)
Traditional PR and marketing is about going out and trying to reach people. The ubiquity of the Internet allows you to let people come to you instead of the other way around.

When you build an audience, you don’t have to buy people’s attention – they give it to you. This is huge advantage.
So build an audience. Speak, write, blog, tweet, make videos – whatever. Share information that’s valuable and you’ll slowly but surely build a loyal audience. Then when you need to get the word out, the right people will already be listening.

Emulate chefs (page 176)
In this chapter the authors make a case for sharing everything you know, something which is anathema in the business world. They use famous chefs as an analogy. The best chefs share their most valuable recipes in their cookbooks. Why? Because they know that their business as a whole cannot be copied. What better way to show you are an excellent cook, then by sharing your recipes?
I am convinced that there are only benefits to sharing everything I know about educational technology and innovation with anybody who is willing to listen. Doing this is the only way to take part in the incredibly valuable discourse on this topic and taking as much out of it as possible.

Forget about formal education (page 215)
Companies still over-value formal education from. I have personally decided to attend as little formal education as possible from here on further. The key qualities that somebody needs to have are curiosity and the ability to learn. If you combine these two, then there is a whole world out there from which you educate yourself. You don’t have to go and sit in a stuffy classroom and listen to some academic lecturing. Don’t get me wrong: academics are hugely valuable. It is just that you don’t have to join a university to engage with them.

Three chapters about things I will try to do from now on:

Embrace constraints (page 67)
This chapter starts as follows:

“I don’t have enough time/money/people/experience.” Stop whining. Less is a good thing. Constraints are advantages in disguise. Limited resources force you to make do with what you’ve got. There’s no room for waste. And that forces you to be creative.

This is a principle that I am already highly aware of (it is actually embedded in every introduction to any Parallax post on this blog). It is not something I am naturally good in though. I love gadgets and these things often create a lot of extra affordances and thus complexity. I need to tone this down to allow a better focus on things that really matter. First step: “downgrade” my current Ubuntu 10.04 setup which allows me a lot of flexibility (and gives me wobbly windows, that’s not me by the way) to the Ubuntu Netbook edition.

Focus on what won’t change (page 85)
This is probably advice that anybody tasked with working on innovation should heed to. Naturally we like to be focussed on the next big thing. The danger is that you will focus on fashion instead of on substance.

The core of your business should be built around things that won’t change. Things that people are going to want today and ten years from now. Those are the things you should invest.

I will try and use this advice while thinking about the next iteration of our learning landscape. Which aspects are lasting needs and wishes and which are just fads?

Interruption is the enemy of productivity (page 104)
I work in an office with about 10 other colleagues (if everybody is in). During a working day I receive about 50 emails in my work Outlook inbox and have multiple instant messaging conversations. This means that I barely have a couple of minutes without any interruptions. I have to admit that I am probably the cause of many interruptions too, as I constantly share the things I find fascinating or funny with my co-workers.
This is definitely not beneficial for my ability to do work on things that require a bit more concentration and need me to be focussed. It takes a lot of time to write anything which is more than a page of two for example. Usually I can only do it if I work from home and I turn Outlook off. From now on I will try to block a couple of hours every week during which I will sit by myself, turn off my phones, IM and email, refuse to look at Google Reader and just work.
It is as the authors say:

Your day in under siege by interruptions. It’s on you to fight back.

Three chapters about things I wish my employer would do going forward:

Meetings are toxic (page 108, available in the free excerpt)
This one is pretty obvious, but we still have a complete meeting culture. Everybody knows that meetings are not very effective at what their intent is to do and still we have way to many. Some of the reasons the authors give for why meetings are this bad are:

  • They usually convey an abysmally small amount of information per minute
  • They require thorough preparation that most people don’t have time for.
  • They often include at least one moron who inevitably gets his turn to waste everyone’s time with nonsense
  • Meetings procreate. One meeting leads to another meeting leads to another…

If you still need to have a meeting I like their simple rules:

  • Set a timer. When it rings, meeting’s over. Period.
  • Invite as few people as possible.
  • Always have a clear agenda.
  • Begin with a specific problem.
  • Meet at the site of the problem instead of a conference room. Point to real things and suggest real changes.
  • End with a solution and make someone responsible for implementing it.

I think we are especially guilty of inviting too many people to meetings and I would love to meet at the site of a problem instead of a conference room, but am not sure how this is done with IT related issues.

Don’t write it down (page 164)
We spend an inordinate amount of time capturing everything everybody says, needs and wants. We have hundreds of Excel files containing lists of requirements, feature/enhancements requests, issues, etc. We probably spend more time managing these spreadsheets than working on the issues that these spreadsheets are an abstraction of.

There’s no need for a spreadsheet, database, or filing system. The requests that really matter are the ones you’ll hear over and over. After a while, you won’t be able to forget them. Your customers will be your memory. They’ll keep reminding you. They’ll show you which things you truly need to worry about.

Don’t scar on the first cut (page 260)

The second something goes wrong, the natural tendency is to create a policy. “Someone’s wearing shorts!? We need a dress code!” No, you don’t. You just need to tell John not to wear shorts again.

This is how bureaucracies are born according to the authors. They consider policies “organizational scar tissue”. I work for a company that, like most other I am sure, is very scarred. Let’s all stop scarring it more!

I have to admit that a list of three was severely limiting when it came to wishes for my employer. I would have like to have the opportunity to add: Ignore the real world (page 13), Illusions of agreement (page 97), Hire managers of one (page 220) and They’re not thirteen (page 255).

Written by Hans de Zwart

06-06-2010 at 10:00

Follow

Get every new post delivered to your Inbox.

Join 895 other followers