Mimi posted something up from Bruce Mau. Mau is often worth reading. He's a design consultant who works with a bunch of people in different disciplines. He co-ordinated the Massive Change show in Canada.

I'm not sure i like manifestos.

There's a whiff of publicity about them.

That or wisdom.

Wisdom doesn't *actually* come in bullet points.

Otherwise we'd all spend weekends poring over Powerpoint presentations.

Actually, ding, that sounds like fun.

Anyway, back to Mau:

Some good points.

Some not so good.

He's wrong when he says,

24. Avoid software. The problem with software is that everyone has it.

Wow, i thought, this is a stunningly damaging point. It's so damaging it could completely nullify any value you might gain from his manifesto.

It's interesting to hear it from an otherwise erudite man. I see where it comes from, but I'm surprised by Mau's naivety. The statement begs closer examination:

It subtly implies a perception of software as finished product, shrink-wrapped result, purpose-built tool, closed package, means to an end, inflexible set of interactions, commoditized form, a creativity curber and probably more.

Another point seems to enforce this vision of technology Mau harbours,

Great liberty exists when we avoid trying to run with the technological pack.

Where dull minds meet technology, dull products - all too easily dictated by the technology - ensue. Tour countless degree shows at Architecture/Art/Design school and cue a thousand reminiscent graphics, fonts-in-common, structures-in-common; a thousand visual signs of technology underused. Spin a thousand electronic music records that scream presets amplified.

Where creative minds meet technology, contemporary statements are made.

You see where i'm going with this.

Aside from all this, plus the flawed logic that ubiquity is harmful, Mau's 24 also completely contradicts point 22,

22. Make your own tools. Hybridize your tools in order to build unique things.

I'd say it is (for architects as for any other creative individual in the 21st century) extremely important to get stuck into software, whether your background is graphics, media, literature, history, whatever.

So let's re-imagine point 24 as,

24. Where existing tools feel foreign, hack them till you feel comfortable in their presence.

Just so i can sleep easy.

miranda says

this post reminds me of an argument i had with a visiting tutor on my graphic design course.


a recent graduate of RCA currently working on an MIT project, his opening point was:


"if you didn't design the program, whatever you make with it isn't yours."


it staggered me that this person wasn't into sharing. a few deep breaths later, the word 'tools' spoken a few times, i could carry on working. it was obvious he wasn't listening.


This post also reminded me of the first project on said course. Entitled "manifesto". I made a jacob's ladder that had written on the ribbon "change is the only constant". My tutors weren't too happy.

anil says

Sounds like your tutor never heard of the GPL, free software or even open source.