[ Content | Sidebar ]

365

December 18th, 2010

Considering re-reading all kinds of classic texts, one a day, in a year. The hardest part, it seems, will be to make a list of what I would read. I started this idea because I thought I wanted to re-read Seneca and Tacitus.

The thoughts on this are here:

http://studiotheory.tumblr.com/post/2352539918/thinking-more-about-this-project-365-books-i

And in this space I am going to start posting the books I think are on the list, in no no order. Thinking out loud still.

  1. The treatise on anatomy of human body and interpretation of philosophers, Itaqi
  2. The book of seasonal periods and sky signs, Ibn al-Ajdabi
  3. The book of knowledge of ingenious mechanical devices
  4. Ibn Khaldun’s philosophy of history
  5. Language, thought and reality, Whorf
  6. The analects of confucius
  7. Mencius
  8. De Anima, Aristotle
  9. The Histories, Herodatus
  10. The Notebooks, Leonardo Da Vinci
  11. Faust
  12. Leviathan, Hobbes
  13. Plato’s Republic
  14. Cicero TBD, probably On Obligations
  15. The Communist Manifesto, Marx
  16. The Golden Bough, Frazier
  17. On The Nature of the Universe, Lucretius
  18. Pascal, Pensées

design research, research for design, research in design

October 21st, 2010

I like research a lot. I don’t like to design without it. Sometimes I can’t figure out how the pieces fit together. I think about this a lot lately, as I am more interested in pure research or applied research than in…well in what? This is where I stumble over design research, and the way that research is thought about in design.

Take interaction design specifically. If you are in industry and you talk about research what you are usually talking about usability or ethnography.

Before the web the people who did the interaction design were engineers or psychologists or human factors specialists. This was not bad, though we might argue it also wasn’t good. I might also argue though that the interfaces designed by engineers for engineers worked for engineers.

With the advent of the web a new class of designers appeared. They were not trained in human factors or HCI, the vacuum was filled with people whose brains were good at organizing and seeing patterns and understanding relationships, it was the wild west and in the early days being good at it was what it took. Education here was often English or library sciences degrees. Engineers were relegated to back rooms.

As the majority of practitioners were not academics, research took on a different meaning, in practice, in industry. It was about making the interface model that existed better, starting from what was all ready known. This resulted in heuristics that became rules of thumb, of pattern libraries that assume most things work reasonably well when they are all the same. Research looked at smaller and smaller elements for usability and ethnography snuck in as understanding the consumers became more important as a point of differentation.

So where then, is the research I love? The cognitive science, neuroscience, decision making models, behavioral economics, psychology, and other fields that inform how and why humans do, act, respond, relate, and interact? Some of it is in research groups within large organizations – Yahoo!, IBM, Microsoft, though I haven’t yet sorted out how the research and the design work to inform each other. Judging by design output and conference papers, I am not sure this is happening, at least not well. At smaller research labs there seems to be more interesting work happening, where research includes science and building in a different relationship. And then there are organizations that seem more focused on pure research, though I cannot tell if and how their work becomes the basis of any of the design that reaches standard consumers.

I wish I better understood these pathways. Design Research as done by people trained in design is inadequate for me as a field, it feels most like an offshoot of consumer marketing. Research within major software/content companies has the strange requirement of insisting on a PhD, which in many cases removes the researcher from some of the reality of design for the real world, which could inform output. And Applied research, pure research, where are you and what are you doing? That which is within universities seems to most pop up at CHI conferences but often the topics are things known by industry practitioners. What use is this? Where are the hybrids which can engage in high level research that could change from the status quo AND can apply it to real world situations?

If you are out there, I’d like to meet you. I need to figure out more context in this realm.

steganographic code

October 20th, 2010

When Dragon Voice first became usable (1993? 1995?) I tried to create a means of speaking code, so i could pace and code. I used both Perl and C as the test languages. It seemed unbearably cool to be able to speak (and compile and run) code without the keyboard as input.

First, to speak code is very difficult and takes far longer than it would to use a keyboard, so the process including finding a means by which to create a spoken code that resulted in transcription to usable end product. Generally, if you code a lot, you type fast. That’s a big hurdle.

So look at the usual starting place:

#include < stdio.h>
void main()
{
printf(“\nHello World\n”);
}

Read it aloud. Takes you longer than it would to type it, right?

So I went about trying to find a language that all ready existed to create a spoken code language that could translate into workable code. I was looking for models of language and grammar that would embody some of what I needed, really, bits and pieces I could borrow to build this new hybrid language.

Thus I found myself elbow deep into Classical Chinese. In classical chinese structure each word is monosyllabic and uses a single character to write it. It is a topic-prominent language, which means that structure can be separate from syntactic ordering of elements. It contains markers and particles.  These all seemed elements that could support spoken code, a simplifying structure. In non-linguistic terms, it gave me a model to build a language on which was both contextual and non-contextual at the same time. It provided flexibility in speech. This becomes even more important when debugging spoken code.

It was easier to work with Perl first as the test model, getting the structures to build with, compilation could come later. I spent a few months building this, and it did work, but basically I had to create a complete language model to support the structure of code, with some english used within the body of the code, depending on purpose and output needs.

It was never faster than typing but it began to create a separate world, an in-language for the people I spoke the code to, and a strange set of code-base behaviors — imagine coding with your hands free.

Why do I write about this? It was interesting, I learned a lot about ancient language models and simplicity, and I think there is still something to it. I am also fascinated by the creation of grammars and the possibility of steganographic code.

behavioral interface design

October 15th, 2010

As a follow up to questions I posted @ekbarbarossa, I have been trying to understand why behavioral economics is considered behavioral economics. Most of the authors of the field are not trained economists. They are psychologists (Tversky, Kahneman), neuroscientists, cognitive psychologists (Ariely) and cognitive scientists. There are those with economics training (Thaler), but then we find them in psych and social science departments at Carnegie Mellon (Lowenstein). They are an interesting group, nonetheless.

It seems to be that their theories, the heuristics — which seem to come from decision making sciences, and framing — which comes from psychology, are used to describe and define behaviors seen in economics. Perhaps as a way to explain why economic theory doesn’t work as is, but needs the irrationality of BE to help explain our actions as humans.

What this does open, for me, is the possibility of more behavioral fields where these theories and perhaps others are applied to both explain how things work and to define new models that are more appropriate, given our behavior.

Where am I going? It seems like there should be a field of behavioral interaction design. Sure, you say, this exists. But does it? Not like this. Interaction design’s heuristics turn man into machine, behavioral economics heuristics explain the ways in which a man is not like a machine.

What happens when I apply these principles of irrationality to to interface design, rather than the concept that man approaches machine? Rationality and logic become the system within which we design using the principles of irrationality to move the user towards outcomes the designer desires.