Hello, my name is Jason Frank. I’m a computer science student at the University of Tennessee and I’m interning here at Sensorpedia this summer. I’m planning to introduce myself more thoroughly with a video blog that I will post in a couple of weeks. Stay tuned… this video will also give you a little behind-the-scenes view of the atmosphere and people of Sensorpedia. In the meantime, let me explore some thoughts and questions that have been posed to me during this internship.
- Does Zen have a place in computer science?
- If users of a simple web app find that they struggle to use it, is it their fault or the the designer’s?
- What visual elements should be included in a web app…or more importantly, which elements should not be included?
So why are these questions relevant to what we do here at Sensorpedia? To answer that, I should tell you a little about my mentor here at Sensorpedia, David Resseguie. David has spent a lot of time studying what is commonly called, “human-computer interaction”. That may sound a little abstract, but really it is just about a user’s experience working with some piece of equipment. A cell phone, for instance. Or you could think of it in terms of everyday household items. My wife can attest to my dislike of standard household lamps. You know how you have to reach your arm down under the lampshade, but then back up next to the bulb and fiddle around trying to find the switch? Yea, bad design. These are the sort of things that David has learned to apply to working with software applications.
Understanding the importance of human-computer interaction, David has instructed us to read some books dedicated to topics in this area. One such book that I have been reading is called, “Presentation Zen” by Garr Reynolds. This book is geared more towards presenting information with the aid of visuals, but I believe its concepts apply to building software applications as well. In the book, Reynolds quotes author John Daido Loori, saying the Zen aesthetic “…reflects a simplicity that allows our attention to be drawn to that which is essential, stripping away the extra.”
So what’s the bottom line? How do we as computer scientists (OK, budding computer scientists) apply these principles? I would say that it is our job as software developers to make the end user’s experience easy and enjoyable. This means we must spend the hours necessary to think through the user’s experience. David is teaching us that we need to ask ourselves the right questions: Where is the user’s eye being drawn? Is that logo really needed on this page? Does the background obscure the text there? Is there something I can leave out to improve the readability? Maybe Zen does have a place in computer science.