A lot of people think dreams and drugs involve some magical inspiration. I think otherwise.
I rarely get inspired by dreams or drugs, but I have my own secret source of inspiration: mishearing other people. Somebody says something, I misinterpret it, and the misinterpretation is quite interesting – more interesting than anything I would have come up with on my own if asked to generate an interesting idea. Maybe it’s a clever joke or turn of phrase. Maybe it’s a neat idea. Sometimes I misunderstand people’s entire positions, and end up with positions much more interesting than the ones they were trying to push.
In the final chapters Bachelard lets slip (a confession really) how if he "were a psychiatrist," he would recommend a poem by Baudelaire to treat "anguish." His squabble then is not with the purpose but rather the approach of a still-young profession. And of course, why not treat the power of great poems as something akin to "virtual 'drugs'"?
Obetrolling didn't make me self-conscious. But it did make me much more self-aware. If I was in a room, and had taken an Obetrol or two with a glass of water and they'd taken effect, I was now not only in the room, but I was aware that I was in the room. In fact, I remember I would often think, or say to myself, quietly but very clearly, 'I am in this room.' It's difficult to explain this. At the time, I called it 'doubling', but I'm still not entirely sure what I meant by this, nor why it seemed so profound and cool to not only be in a room but be totally aware that I was in the room.
You just handed off a major redesign. Three months of research, twenty-seven major revisions, and hundreds cups of coffee have all culminated in this pinnacle of glory. It’s finally done!
Except it’s not.
It’s not, even after you have answered every single question the developers have about your red-line.
It’s not, even after you have addressed all the technical constraints developers encountered during the implementation.
It’s not, even after you meticulously documented all the patterns and styles into a library for reference and reuse.
It’s not, because neither you nor the developers have talked to a real user. At the bottom of your heart, you are secretly wishing:
My design looks great on paper, so let’s keep it on paper.
Post-occupancy evaluation (POE) is a practice in the building industry where an architect would visit the building after its occupancy and interview its residents. It sounds like a great opportunity for collecting feedback and learning from mistakes, but it’s rarely practiced. Why?
Many awe-inspiring, prize-winning architectures are half building, half sculpture. Often made of specially molded concrete and steel, they are extremely expensive to alter, let alone any alteration would also attack the architect’s prestige and pride. So whatever usability issues the POE identifies will remain as issues, unless the architect wants to accept the public criticism and shame that comes with the remodeling.
In fear of criticism, an architect would turn down the opportunity for POE, and continue to design the same roof that would leak water in future projects.
In fear of criticism, a developer would use customer service representatives as a shield against user complaints, while focusing on the “technical” aspect of things.
In fear of criticism, a designer would close the contract as soon as the client accepts the design, even though none of the real users are represented by the client.