There's always a danger, when you start into describing the operation of the human mind in order to describe how to get something done (e.g. design a building). It's tempting to reduce the entirety of human perception down to a simple metaphor or process, something that can be readily understood. The problem is, human perception and cognition are fairly complex phenomena, so if you find a good metaphor, you get a good story, and something quite comprehensible, but not a particularly good way of understanding how perception works.
Norberg-Schulz has, I believe, described a good tool for the architect in thinking about and manipulating space, but he hasn't encompassed the entirety of our understanding of design and architecture. That is, while our sense of "place" and our sense of "path" are interesting, and they can be used as a generative/organising principle (e.g. in Casa Andreis), they don't particularly describe the totality of what is needed to understand "good architecture".
The approach can even be seen as a good tool for analysis of designs, but it leaves so much out that it isn't so much a theory of asthetics as a particular practical tool to be applied to the problem of design which has a basis in an observed perception (sense of space and place).
What was particularly interesting to me was that, though I've read about the path-and-place approach to design, I didn't cover it explicitly in my thesis. The general patterns to which it conforms are there, but the particular emphasis was not discussed.


Comments
2010-07-25 14:02
> and would have no Trac integ ration The trac-bzr plugin[ 1] seems to provide good integ ration between bzr and t [...]
2010-07-13 21:47
I've always been fascinated wi th the Asterisk AMI interface. So much so that I married tha t fascination with the [...]
2010-07-03 21:32
Yes, only references in dicti onaries are replaced, so hold ing references in lists, tuple s, etceteras keeps them alive.
2010-07-03 11:18
They hold references to remove and install?
2010-06-24 08:34
There's higher-level objects w hich are tracking what is repl aced (the actual Mock objects) . They hold references [...]
2010-06-24 08:23
I haven't tried it, but it see ms to me like this approach ha s one fundamental problem: If you replace all refs o [...]
2010-06-24 08:22
That's the "magic" that made m e go "ooh shiny"
2010-06-24 06:03
That's even more evil than the mock patch decorator...
2010-06-06 18:33
blush Oh.
2010-06-06 11:07
That's what the module does (a utomatically), but on a per-te st-run basis, and only for the process being tested (i [...]
2010-06-06 02:43
Maybe I'm missing something im portant here, but why not just write small scripts to mimic whatever dangerous utili [...]
2010-06-05 15:17
I thought about stubbing out t he python call to the process in the current process, but I want something which stu [...]
2010-06-05 14:47
Hmm... if Mock isn't flexibl e enough to handle mocking pro cesses adequately then I'd lik e to know how it could b [...]
2010-05-19 10:27
Hey, maybe it's a stupid new bie question, but where and ho w exactly should the patching of the core take place? [...]
2010-05-04 14:36
I used Qemu and VirtualBox pre tty extensively back when I wa s working for the OLPC, but mo st of the stuff we were [...]