Friday, July 16, 2010
Finally in Maryland
I'm hoping to keep up my blog on what I'm doing outside of work here in Maryland, so people back home in Ansteorra/Texas will know. I don't know how often I'll be able to update this, but we'll see. In the next couple of days, I'll hopefully be posting a few pics and thoughts from my drive from Texas to Maryland.
Monday, May 4, 2009
Fitts' Law
Fitts' Law is very curious. It is a model of human movement which predicts the time to move a mouse/cursor/etc to a certain target area. The work for this was done back in 1954, and has many implications for design then as well as modern and future design.
The way humans move has not changed for years, and will not change quickly. What this law tells us is that in designing new interfaces, we need to be aware of the time it takes for a person to find and select an icon. This time can affect how well the user likes the program. So, when designing an interface, one should be aware of the size of their icons and buttons, since it could influence how users like and/or enjoy the program/device.
The way humans move has not changed for years, and will not change quickly. What this law tells us is that in designing new interfaces, we need to be aware of the time it takes for a person to find and select an icon. This time can affect how well the user likes the program. So, when designing an interface, one should be aware of the size of their icons and buttons, since it could influence how users like and/or enjoy the program/device.
Thursday, April 30, 2009
How do people use computers?
My CHI09 paper is called Computer Usage in Daily Life, by Thomas Beauvisage.
This paper is about a study of French participants that determined the different types of computer users there are, and created generalizations of this that could affect future design of computer interfaces. In my reading, I focused on the basic methods of the study and the results over the way the results were generated.
The French participants were recruited by phone and internet. Because of the nature of the study, all members of the family were required to participate. Overall, the panel included 661 households and 1434 individuals. The families installed a tracking application on their computer, which, once running, appeared as an icon in the system tray.
The study generated five computer usage day profiles, four household profiles, and five individual profiles.
The computer usage day profiles are:
Household Profiles:
1. PC 24/24 - 15%
2. Always available- 33%
3. PC on demand- 30%
4. Low usage- 22%
Individual Profiles:
After this study, they found three implications for design:
1. Operating System design: They believe it could enhance user experience by making computers boot faster. This would be better for the PC on demand and low usage groups.
2. Application and service design: They feel that in application design, the features only need to address one or two of the different groups, instead of trying to please all of the groups.
3. Web services design: "Providing new services as Web services rather than casual application appears to be a key for success."
Overall, this was an interesting paper. While I don't doubt that they got a decent representative group, it would be interesting to see what the results would be in America, or a different country.
Other interesting data:
Link to the paper here.
This paper is about a study of French participants that determined the different types of computer users there are, and created generalizations of this that could affect future design of computer interfaces. In my reading, I focused on the basic methods of the study and the results over the way the results were generated.
The French participants were recruited by phone and internet. Because of the nature of the study, all members of the family were required to participate. Overall, the panel included 661 households and 1434 individuals. The families installed a tracking application on their computer, which, once running, appeared as an icon in the system tray.
The study generated five computer usage day profiles, four household profiles, and five individual profiles.
The computer usage day profiles are:
Household Profiles:
1. PC 24/24 - 15%
2. Always available- 33%
3. PC on demand- 30%
4. Low usage- 22%
Individual Profiles:
After this study, they found three implications for design:
1. Operating System design: They believe it could enhance user experience by making computers boot faster. This would be better for the PC on demand and low usage groups.
2. Application and service design: They feel that in application design, the features only need to address one or two of the different groups, instead of trying to please all of the groups.
3. Web services design: "Providing new services as Web services rather than casual application appears to be a key for success."
Overall, this was an interesting paper. While I don't doubt that they got a decent representative group, it would be interesting to see what the results would be in America, or a different country.
Other interesting data:
Link to the paper here.
Thursday, April 23, 2009
Usability Evaluation Considered Harmful (Some of the Time)
This paper is by Saul Greenberg and Bill Buxton. The point of this paper is to point out that usability evaluations are not always the best means to test a product. The authors seem to think that usefulness tests would be better. However, these are hard to do, since it is always unknown how useful people will find a product. They also believe that tests appear to be almost required, and this should not necessarily be so.
The authors make some good points in this essay. However, I do not see usability evaluations disappearing in the near future. But it would be nice if there were other methods to evaluate products that might give a better understanding of how they would be taken out in the world.
The authors make some good points in this essay. However, I do not see usability evaluations disappearing in the near future. But it would be nice if there were other methods to evaluate products that might give a better understanding of how they would be taken out in the world.
Harmful or Not: Human-Centered Design
I recently read a paper by Don Norman (oh my gosh! Another Norman writing!), called Human-Centered Design Considered Harmful.
Norman's main point of this paper is that design ought to be activity centered, and not human centered. The reason for this is that people do things on a computer for an activity or job. So the design of the program ought to be for what that activity or job is. One of his points is that people adapt to the tools.
I think he makes a good point in that activity centered design is important. I also think that the idea that people adapt to the tools is possibly true. However, people also adapt the environment to fit them. How else would the early humans have gotten tools in the first place? Maybe I'm hitting the wrong point, but that's what I think.
Norman's main point of this paper is that design ought to be activity centered, and not human centered. The reason for this is that people do things on a computer for an activity or job. So the design of the program ought to be for what that activity or job is. One of his points is that people adapt to the tools.
I think he makes a good point in that activity centered design is important. I also think that the idea that people adapt to the tools is possibly true. However, people also adapt the environment to fit them. How else would the early humans have gotten tools in the first place? Maybe I'm hitting the wrong point, but that's what I think.
Tuesday, April 21, 2009
Methods of Collecting Internet Content
My UIST 07 paper is called Relations, Cards, and Search Templates: User-Guided Web Data Integration and Layout by Mira Dontcheva, Steven M. Drucker, David Salesin, and Michael F. Cohen.
This paper was about the three methods of organizing internet data that the writers had designed. The first is an interaction technique based on relations, linking different websites and allowing users to automatically extract content from these websites. The second is a way of merging content from these websites and being able to organize it visually in a way easy for the user to see. The third involves search templates to allow users to search faster for the information they want.
The relation-based interaction technique works when a user clicks to extract certain data from one website, and then gets information for the same company/restaurant/etc from a different website. They have the option of linking the two websites together. After that, when the user goes to one of the linked websites, the program will automatically pull the related information from the other website(s).
The organization of the content of these websites is done with the second method. A card is created with this information. Then the user can organize the data on these cards in any order they want. After they set the first card, all other cards will be set up the same way.
The search templates work similarly. They start with having a card and search template which has relations in it that say what website information goes where. Then the user can select a search template and type in their search query.
This seems like a very useful piece of software. It would enable many people to do more efficient searches that would save them a lot of time.
This paper was about the three methods of organizing internet data that the writers had designed. The first is an interaction technique based on relations, linking different websites and allowing users to automatically extract content from these websites. The second is a way of merging content from these websites and being able to organize it visually in a way easy for the user to see. The third involves search templates to allow users to search faster for the information they want.
The relation-based interaction technique works when a user clicks to extract certain data from one website, and then gets information for the same company/restaurant/etc from a different website. They have the option of linking the two websites together. After that, when the user goes to one of the linked websites, the program will automatically pull the related information from the other website(s).
The organization of the content of these websites is done with the second method. A card is created with this information. Then the user can organize the data on these cards in any order they want. After they set the first card, all other cards will be set up the same way.
The search templates work similarly. They start with having a card and search template which has relations in it that say what website information goes where. Then the user can select a search template and type in their search query.
This seems like a very useful piece of software. It would enable many people to do more efficient searches that would save them a lot of time.
Thursday, April 16, 2009
Inmates? Running the Asylum? We're in trouble!
I recently finished reading The Inmates are Running the Asylum by Alan Cooper. This was a very interesting read.
The book starts out by giving examples of what happens when computerized systems start being integrated in many different system. These examples were sometimes highly amusing, but most of the time dealt with important systems that failure causes enormous amounts of damage.
The author then goes on to tell of company blunders dealing with design, and design blunders in general. Then he mentions some of the things one can do about it. He states a method of design he feels would work well to take care of design issues.
I think this book seemed like it was trying to target multiple audiences for multiple parts of the book. Some of it aimed at developers and some of it aimed at managers. This made it a little bit harder to read, since the writing style was changing as we were going through the book. However, he made some very good points about the development process and the importance of design in the process. Overall, I enjoyed reading this book.
The book starts out by giving examples of what happens when computerized systems start being integrated in many different system. These examples were sometimes highly amusing, but most of the time dealt with important systems that failure causes enormous amounts of damage.
The author then goes on to tell of company blunders dealing with design, and design blunders in general. Then he mentions some of the things one can do about it. He states a method of design he feels would work well to take care of design issues.
I think this book seemed like it was trying to target multiple audiences for multiple parts of the book. Some of it aimed at developers and some of it aimed at managers. This made it a little bit harder to read, since the writing style was changing as we were going through the book. However, he made some very good points about the development process and the importance of design in the process. Overall, I enjoyed reading this book.
Thursday, March 12, 2009
Reading Books Online
The CHI2008 paper I read was called "Readability of Scanned Books in Digital Libraries," by Alexander J. Quinn, Chang Hu, Takeshi Arisaka, Anne Rose, and Benjamine B. Bederson.
The focus of the paper is on making scanned books easier to read online. The main type of book they talked about are children's books. In these books, the images can be nearly as important as the text. How the text is displayed can also be important. The writers have come up with two solutions to this problem.
The first is called ClearText, and it is when the text in the page is taken out and rendered in the font set of the user's machine. This makes it possible to "resize the text without resizing the background." It also would help towards the translation of the text for readers of other languages. However, problems come up when dealing with the font size. If the font gets too large, then it could obscure the image. There is also the issue of what the font size should be when switching between pages. They determined that there should be a maximum font size allowed based on the page with the most text.
The second is called PopoutText. This leaves the text as is in the picture/page, but it makes a sort of cut-out of it that can be clicked on and popped out of the image with greater magnification. The advantage of this is that the text stays the same, and the imagery with the text, if there is anything, will remain. However, this does not lend itself for translations of the text.
The writers then compared these two methods with the current method of online books. This method shows the image, and the user must magnify the image to see all the text. Then they must scroll around the page to find all the wording, and sometimes this can be a challenge, depending on the size of their screen.
I really enjoyed reading this paper. I can see these sorts of things coming into standard use, especially as more and more material starts appearing on the internet. Personally, I don't like reading things online, and part of the reason for this is in fact the smaller resolution of the screen. The writers mention this as one of their reasons for creating these interfaces. It looks like they have a good base, and I hope to see this come into more standard use in the future.
Link to paper
The focus of the paper is on making scanned books easier to read online. The main type of book they talked about are children's books. In these books, the images can be nearly as important as the text. How the text is displayed can also be important. The writers have come up with two solutions to this problem.
The first is called ClearText, and it is when the text in the page is taken out and rendered in the font set of the user's machine. This makes it possible to "resize the text without resizing the background." It also would help towards the translation of the text for readers of other languages. However, problems come up when dealing with the font size. If the font gets too large, then it could obscure the image. There is also the issue of what the font size should be when switching between pages. They determined that there should be a maximum font size allowed based on the page with the most text.
The second is called PopoutText. This leaves the text as is in the picture/page, but it makes a sort of cut-out of it that can be clicked on and popped out of the image with greater magnification. The advantage of this is that the text stays the same, and the imagery with the text, if there is anything, will remain. However, this does not lend itself for translations of the text.
The writers then compared these two methods with the current method of online books. This method shows the image, and the user must magnify the image to see all the text. Then they must scroll around the page to find all the wording, and sometimes this can be a challenge, depending on the size of their screen.
I really enjoyed reading this paper. I can see these sorts of things coming into standard use, especially as more and more material starts appearing on the internet. Personally, I don't like reading things online, and part of the reason for this is in fact the smaller resolution of the screen. The writers mention this as one of their reasons for creating these interfaces. It looks like they have a good base, and I hope to see this come into more standard use in the future.
Link to paper
Saturday, February 28, 2009
Homes, Robots, and Cars, Oh My!
Regarding Don Norman's "The Design of Future Things", there were several things I found interesting. First off, compared to "The Design of Everyday Things," the examples were completely relevant to our modern time. However, he seemed to use the same ones all the time. These are homes that will try to predict your needs and wants, and cars that will be able to drive you themselves without any human intervention.
I really don't know about anyone else, but I find the idea of technology that just does stuff for us to be a little strange. I realize that some of this sort of stuff already exists, and we're used to it. These are things like clothing factories that automatically make clothing. People used to do this themselves, to a certain extent, but it's become a thing where it's somewhat surprising when someone owns a sewing machine and can use it. I happen to be part of a group that makes our own historical clothing to do reenactment, so I'm slowly learning how to use a sewing machine, and my roommate certainly does.
But things like your scale telling your refrigerator what you shouldn't have for breakfast just because you've gained a little bit of weight? At this point, it seems a little off the top. The scale would need to be able to do so much in order to figure out how much weight is fat and how much is muscle. I know of someone who was told she was overweight for her height. She's a short muscular person in top condition. It's all muscle.
And cars that can drive themselves. At this point, it sounds kinda scary to me. I suppose that I just don't trust the technology we have today. Sometimes I wonder whether it is because I'm a computer scientist that I don't trust technology. Or for the same reason that I want to feel more in control of it, or that I understand what it's doing, and I can see potential for failure.
Overall, the book was well-written, and provoked interesting thoughts.
I really don't know about anyone else, but I find the idea of technology that just does stuff for us to be a little strange. I realize that some of this sort of stuff already exists, and we're used to it. These are things like clothing factories that automatically make clothing. People used to do this themselves, to a certain extent, but it's become a thing where it's somewhat surprising when someone owns a sewing machine and can use it. I happen to be part of a group that makes our own historical clothing to do reenactment, so I'm slowly learning how to use a sewing machine, and my roommate certainly does.
But things like your scale telling your refrigerator what you shouldn't have for breakfast just because you've gained a little bit of weight? At this point, it seems a little off the top. The scale would need to be able to do so much in order to figure out how much weight is fat and how much is muscle. I know of someone who was told she was overweight for her height. She's a short muscular person in top condition. It's all muscle.
And cars that can drive themselves. At this point, it sounds kinda scary to me. I suppose that I just don't trust the technology we have today. Sometimes I wonder whether it is because I'm a computer scientist that I don't trust technology. Or for the same reason that I want to feel more in control of it, or that I understand what it's doing, and I can see potential for failure.
Overall, the book was well-written, and provoked interesting thoughts.
Tuesday, February 24, 2009
Tour Video Paper
The paper I read is called "Creating Map-based Storyboards for Browsing Tour Videos" by Suporn Pongnumkul, Jue Wang, and Michael Cohen. It is over the author's tool to allow people who make videos as they travel places to make a more comprehensive and informative tour guide-like portfolio. The tool takes in the video sequence, and pre-processes it to determine feature points for both quality measurement and identifying coherent shots. This pre-processing then creates a coherence matrix to help pick out the interesting shots that will be used to generate the final set of coherent shots. The authoring part of their program is where the user interface comes in. This is where the user can start creating their storyboard presentation. The third part of the tool is the viewing tool, where the user can view the videos and explore the locations of the scenes.
This sounds like an interesting tool that might make tour video processing much easier. What I liked is that they did a user study of the product (minus the pre-processing, since that would have been harder on the participants), and were well aware of the limitations of their testing. The authors seem to have a good plan for future changes and testing as well. I thought that this would be a great tool to have, if I ever found myself in a position to do something of this sort. However, I'm not sure if they really know whether this tool would be good for basic users, or those not used to working with computers. The participants of the testing were all major computer users. Also, their sample size of 13 seems a little low, but there could have been other limitations that affected this.
The above is the viewing tool of their program.
Below is the viewing tool, which is a web-based interface.
This sounds like an interesting tool that might make tour video processing much easier. What I liked is that they did a user study of the product (minus the pre-processing, since that would have been harder on the participants), and were well aware of the limitations of their testing. The authors seem to have a good plan for future changes and testing as well. I thought that this would be a great tool to have, if I ever found myself in a position to do something of this sort. However, I'm not sure if they really know whether this tool would be good for basic users, or those not used to working with computers. The participants of the testing were all major computer users. Also, their sample size of 13 seems a little low, but there could have been other limitations that affected this.
The above is the viewing tool of their program.Below is the viewing tool, which is a web-based interface.
Both images taken from the paper directly. All rights to the writers.
Thursday, February 19, 2009
The Mole People
I read "The Mole People" by Jennifer Toth. Overall, it was an interesting book. It was written more like a series of short stories than a chapter book with a plot. This made it a little easier to read, since you don't always have to remember what happened before, but also she talked to so many people that the names just started merging as I continued to read the book. I started having problems remembering who was who, and what sort of situation they were living in.
The book starts out describing her troubles getting information out of the authorities above ground, since they were trying to keep the fact that there were people living in the tunnels a secret. I can understand what they were thinking, in that they don't want people to panic about it. However, I don't see that they gain any real benefits from that. I think that if people found out on their own, then there'd be more panic than if they were already informed about it.
I think Ms. Toth is really brave for doing this research. She was going down into these tunnels to meet the underground dwellers. This would have been incredibly dangerous and she could have lost her life. On the other hand, I don't think she would have gotten as much information had she not done this. However, I think if she had had a partner working with her, then it might have been safer for her. And there might have been a little more data collection as well, because they can look for different things.
So, as a book, it was enlightening to see what sort of living situations the tunnel dwellers have, and realizing that this could have easily have happened elsewhere besides New York. It just happens that it is a heightened issue because of the number of tunnels beneath the city.
The book starts out describing her troubles getting information out of the authorities above ground, since they were trying to keep the fact that there were people living in the tunnels a secret. I can understand what they were thinking, in that they don't want people to panic about it. However, I don't see that they gain any real benefits from that. I think that if people found out on their own, then there'd be more panic than if they were already informed about it.
I think Ms. Toth is really brave for doing this research. She was going down into these tunnels to meet the underground dwellers. This would have been incredibly dangerous and she could have lost her life. On the other hand, I don't think she would have gotten as much information had she not done this. However, I think if she had had a partner working with her, then it might have been safer for her. And there might have been a little more data collection as well, because they can look for different things.
So, as a book, it was enlightening to see what sort of living situations the tunnel dwellers have, and realizing that this could have easily have happened elsewhere besides New York. It just happens that it is a heightened issue because of the number of tunnels beneath the city.
Forum Ethnography
I must admit, I was a little wary about doing an ethnography at first. I am no good at inserting myself into a place where I can make observations about a group of people. However, I think the ethnography I did with Kevin Kwan worked pretty well.
Considering that we weren't exactly seeing the people posting on the forum, I think we were able to see some good data on them. I personally don't post on forums at all, so this was entirely new to me. Some of the comments were highly entertaining, while others I felt were somewhat inappropriate. On the other hand, though, Kevin made it sound ike these sorts of comments are fairly normal. From what I know in real life, sheltered as I have been, I realize that these sorts of comments are more than likely used off the internet as well. Of course I know I can't completely generalize online forum thread posting with offline discussions. This is because once a discussion is off-topic in a person to person conversation, it will typically stay off-topic, especially if there are lots of people. It will, on occasion, come back to topic if it's more a question and answer session.
...I just realized that I linked our forum ethnography to real life. This is something I hadn't thought of originally, nor when I was working on the paper for the ethnography. But, people are the same either posting online or having a conversation. The type of person doing each might be different (since when you post online you're more hidden from other posters), but overall what they tend to say will be similar.
So, I hope I've hit something I should be blogging about. I more or less ended up off-topic. In the long term, though, this is what I got out of the ethnography I did with Kevin after letting it sit in my mind and mulling it over a little.
Considering that we weren't exactly seeing the people posting on the forum, I think we were able to see some good data on them. I personally don't post on forums at all, so this was entirely new to me. Some of the comments were highly entertaining, while others I felt were somewhat inappropriate. On the other hand, though, Kevin made it sound ike these sorts of comments are fairly normal. From what I know in real life, sheltered as I have been, I realize that these sorts of comments are more than likely used off the internet as well. Of course I know I can't completely generalize online forum thread posting with offline discussions. This is because once a discussion is off-topic in a person to person conversation, it will typically stay off-topic, especially if there are lots of people. It will, on occasion, come back to topic if it's more a question and answer session.
...I just realized that I linked our forum ethnography to real life. This is something I hadn't thought of originally, nor when I was working on the paper for the ethnography. But, people are the same either posting online or having a conversation. The type of person doing each might be different (since when you post online you're more hidden from other posters), but overall what they tend to say will be similar.
So, I hope I've hit something I should be blogging about. I more or less ended up off-topic. In the long term, though, this is what I got out of the ethnography I did with Kevin after letting it sit in my mind and mulling it over a little.
Thursday, February 12, 2009
Media Equation
This book was focused around the subject of using already established psychological knowledge and applying it to media and computers. Reeves and Naas basically took all of the statements and replaced the secondary human in the statement with 'computer', or some form of that. Then they tested to see whether these statements still hold true. The basis of the book was to describe the experiments they did and explain the results.
Personally, I wasn't as fond of this book as I was of 'The Design of Everyday Things'. However, there were a few things I thought of initially as I was reading the first few chapters of the book. They seemed to keep expounding on the fact that people tend to treat computers and media as if they were real people. While I don't agree with them, I do know that I personally have named several pieces of my electronics, but that is mainly to keep them straight in my mind. I don't give them personalities. Sometimes I'll get frustrated at my computer and talk to it like it's got a personality, but I know it doesn't.
One of the other things I thought of while thinking along those lines is the fact that I am a computer science major. I work with computers, and have been dealing more closely with computers than the general populace has. So I was wondering whether this is the main reason I don't really think of media as being real (based on my impression of the definition of real in the book) is because of this. However, I realize that they mentioned that some of the people for one of their studies were fairly knowledgeable about computers, and could have programmed the programs they were using for the study. I just don't think that computers should be praising themselves, or making comments that are human-like, either praising the user or otherwise. If it was a human-like face on the screen doing that, then I can see it happening. But a spell check should NOT be saying things like 'you spelled this hard word correctly. congratulations!'...
Another thought I had concerned their idea of size and clarity of the image or sound. I don't think that people actually think of the media hardware as being 'real', but that they might instead be thinking about themselves being in the same place as what they are watching. This is one of the points I don't think I really understand about it. Also, a computer screen is much closer to you than a TV normally would be. I don't remember if they mentioned taking this into account or not when explaining their different experiments.
Overall, it is a decent book. I think those who are going into a field where they need to be able to interact with people should read this book, but in my experience as a computer scientist, I don't particularly agree with their point of view, nor think that it is a priority to read this book.
Commented on George's blog entry for this book.
Personally, I wasn't as fond of this book as I was of 'The Design of Everyday Things'. However, there were a few things I thought of initially as I was reading the first few chapters of the book. They seemed to keep expounding on the fact that people tend to treat computers and media as if they were real people. While I don't agree with them, I do know that I personally have named several pieces of my electronics, but that is mainly to keep them straight in my mind. I don't give them personalities. Sometimes I'll get frustrated at my computer and talk to it like it's got a personality, but I know it doesn't.
One of the other things I thought of while thinking along those lines is the fact that I am a computer science major. I work with computers, and have been dealing more closely with computers than the general populace has. So I was wondering whether this is the main reason I don't really think of media as being real (based on my impression of the definition of real in the book) is because of this. However, I realize that they mentioned that some of the people for one of their studies were fairly knowledgeable about computers, and could have programmed the programs they were using for the study. I just don't think that computers should be praising themselves, or making comments that are human-like, either praising the user or otherwise. If it was a human-like face on the screen doing that, then I can see it happening. But a spell check should NOT be saying things like 'you spelled this hard word correctly. congratulations!'...
Another thought I had concerned their idea of size and clarity of the image or sound. I don't think that people actually think of the media hardware as being 'real', but that they might instead be thinking about themselves being in the same place as what they are watching. This is one of the points I don't think I really understand about it. Also, a computer screen is much closer to you than a TV normally would be. I don't remember if they mentioned taking this into account or not when explaining their different experiments.
Overall, it is a decent book. I think those who are going into a field where they need to be able to interact with people should read this book, but in my experience as a computer scientist, I don't particularly agree with their point of view, nor think that it is a priority to read this book.
Commented on George's blog entry for this book.
Thursday, January 29, 2009
UI for Consideration
The device I decided to consider was my portable cd player. Overall, it's a nice player, but it has some features that can be hard to decipher.The front interface is around a circle in the middle. The volume buttons are on the top, one with a plus sign and one with a minus sign and with the abbreviation 'vol' next to it, so one knows exactly what those buttons do. The next and previous buttons are next going clockwise around the outside circle. These are relatively well labeled, but unless you know what the symbols mean, you might not be able to understand what it wants you to do. This also goes for the play/pause button and the stop button, which are the next ones around that outer circle. One good thing about the play/pause button is that there is a raised dot on it, much like the raised bars on the f and j keys on the keyboard, which helps me know which button it is, and be able to find the other major buttons. The rest of the buttons around that inner circle are the ones that can be more confusing. The radio/band and tuning mode buttons are easy to use. They only have one function. Same goes for the equalizer button, but you need to know what eq stands for to understand that. The last three buttons take some getting used to. These have more than one function. I mainly use the farthest one if going clockwise from the top. This is the play mode button. I don't know what exactly the other function does (-city/nor...???), but when playing a cd, this button allows you to change between repeating a single song, repeat the cd, shuffle once through the songs, or shuffle and repeat all the songs. The third of those is not available for use when an mp3 cd is inserted, much to my dismay, but I've gotten used to it.
One feature that is only really explained in the manual is that the radio uses the headphone cord to find the signal. Unfortunately, the headphones I got with the player broke a year after I got it, and it's been a while since then (and I rarely use the radio function on it anyway) so I don't remember whether the quality changed after that.
Overall, I really like my cd player, but for some of the special functions beyond those that are basic, I would definitely need a manual. This is because some of the buttons have more than one function.
Wednesday, January 28, 2009
Comments on Design of Everyday Things
This book was interesting to read. Don Norman, the author of the book, talks initially about those things that cause people issues in everyday life. Some examples are the phone system at people's work places, different types of doors (those that cause problems are those that have no visible sign on which way they open, or give mixed signals), and other sorts of things. Later in the book, he describes several different aspects of design, and explains what one must think about when they design objects.
Overall, I enjoyed the book. There were a few things I noticed as I was reading the later chapters of the book. One was that the examples seemed a little bit out of date. Granted, the original version of the book was published in 1988, and this edition doesn't have much changed from the original. I can see the relevance of all the examples, and can relate to them myself. But I can see that many of these examples would have to change for the next generation, as well as some of the text. My younger brothers might know what a typewriter is (barely), and I used one myself, but many of the next generation after mine don't know what a record player is, and might not even know what a typewriter is. Another possibility is that in a couple generations, there might not be land line phones at all. With the way technology has grown exponentially, land line phones could possibly become a thing of the past as the populace turns to cell phones and iPhones and similar devices, especially those which can access the internet as well as being used as phones. There were also many ideas mentioned which have been implemented already. This was the main thing I noticed as I read the book. Despite this, the information he wrote about is still relevant to today. There are still issues with designs of all sorts of things, and I've been noticing those things that are not as well designed ever since I started reading this book.
Commented on Steven's blog.
Overall, I enjoyed the book. There were a few things I noticed as I was reading the later chapters of the book. One was that the examples seemed a little bit out of date. Granted, the original version of the book was published in 1988, and this edition doesn't have much changed from the original. I can see the relevance of all the examples, and can relate to them myself. But I can see that many of these examples would have to change for the next generation, as well as some of the text. My younger brothers might know what a typewriter is (barely), and I used one myself, but many of the next generation after mine don't know what a record player is, and might not even know what a typewriter is. Another possibility is that in a couple generations, there might not be land line phones at all. With the way technology has grown exponentially, land line phones could possibly become a thing of the past as the populace turns to cell phones and iPhones and similar devices, especially those which can access the internet as well as being used as phones. There were also many ideas mentioned which have been implemented already. This was the main thing I noticed as I read the book. Despite this, the information he wrote about is still relevant to today. There are still issues with designs of all sorts of things, and I've been noticing those things that are not as well designed ever since I started reading this book.
Commented on Steven's blog.
Wednesday, January 21, 2009
Explanation of the name, just because
Just because I feel like making a first post before any class ones, and I think some of my friends might be interested (though maybe not those in my class who will be looking at this blog), I decided to explain where I got the name for my blog.
There is an album I've listened to which contains solely Turloch O'Carolan songs. For those who don't know, Turloch O'Carolan is a famous Irish harper who was blind. There is one song on this album called Carolan's Rambles to Teague. It is a solo wooden flute (or at least it sounds like a wooden flute to me), and the way it is recorded it sounds very hallow and echoing. I love the song. I've looked up information about it, and it's variations on a song called 'When she cam ben'.
So, I was here thinking about the name for my blog, and I knew that I'd probably be rambling on about the books and articles I will have to read for class (and possibly other things), I thought of this song. Then I decided to name my blog 'Sarah's Rambles to Teague'.
And on another note, my blogs are signed Brigid. This is the name I have taken for the Society for Creative Anachronism. It's a Medieval and Renaissance reenactment group in which you take a name and pick a place you are from, and pretend you are a person who could possibly live there during a particular time. So you are not being a true historical person; just someone who would have been there at that time. Now you know why I'm signing Brigid instead of Sarah.
There is an album I've listened to which contains solely Turloch O'Carolan songs. For those who don't know, Turloch O'Carolan is a famous Irish harper who was blind. There is one song on this album called Carolan's Rambles to Teague. It is a solo wooden flute (or at least it sounds like a wooden flute to me), and the way it is recorded it sounds very hallow and echoing. I love the song. I've looked up information about it, and it's variations on a song called 'When she cam ben'.
So, I was here thinking about the name for my blog, and I knew that I'd probably be rambling on about the books and articles I will have to read for class (and possibly other things), I thought of this song. Then I decided to name my blog 'Sarah's Rambles to Teague'.
And on another note, my blogs are signed Brigid. This is the name I have taken for the Society for Creative Anachronism. It's a Medieval and Renaissance reenactment group in which you take a name and pick a place you are from, and pretend you are a person who could possibly live there during a particular time. So you are not being a true historical person; just someone who would have been there at that time. Now you know why I'm signing Brigid instead of Sarah.
Subscribe to:
Posts (Atom)