(by Malcolm McCullough November + December 2012 DOI: 10.1145/2377783.2377793)
Fantastic text. I came [to the interactions website] by searching for people who quote the Stanford study on multitasking. The introduction is fantastic as it builds up an argument that attention has some features that do not change over time.
(by Gilbert Cockton November + December 2012 DOI: 10.1145/2377783.2377786)
The author overlooks the important issue that the "big boys" largely do not appreciate the need for design and the problems that real people have with technology. I admit that we've had a hard time selling UCD but I am not persuaded by the arguments here to abandon it. Perhaps have a look at my article on a similar subject, "User Requirements for the 21st Century," where I take a more pragmatic view of trying to address real users' needs in the development process: http://bit.ly/agile-ucd
Creating the World Citizen Parliament
(by Doug Schuler, May + June 2013 DOI: 10.1145/2451856.2451867)
Not wanting to do anything so grandiose as building a (technology for) a world parliament, I have in essence been working on the same problems and facing the seven challenges with a project called COMPANY (https://gust.com/c/littleelephantltd).
In 2011, working with senior software developersgratis, although neither the ethical undertaking nor the promise of sweat equity were enough to keep them involvedI established the technical feasibility of COMPANY.
In 2012, turning from the "voluntary, principled" participation modelbecause the attractions of real paying jobs had lost me my teamI received financial support from the New Zealand government. This partially funded an Intellectual Property Position Review, which the government considered a pre-requisite as commercial due diligenceto investing in an initial build or beta. The IPPR recommended I do proceed. However, the government offers only partial funding and without a team, either technical or commercial, there has been little to no investor interest.
As things stand at present, I have the tools and schematics for a beta build of something that would fit the sort of use imagined here. If you have any interest in helping, please contact me.
Blog: Enlightenment by lesson, rather than by lecture
(by Tek-Jin Nam; http://interactions.acm.org/blog/view/enlightenment-by-lesson-rather-than-by-lecture)
I think this content will be very helpful for lecturers and professors who teach design courses!!
(by Jonathan Grudin; http://interactions.acm.org/blog/view/couch-potato-u)
My opinion is that you have posed some of the correct questions in this blog post. Journalists who cover business and education have in my reading either not posed any questions or posed only inconsequential questions about MOOCs. I agree with Amelia Abreu that pedagogical questions are important, but your personal reflection on broadcast viewing seems more decisive to me.
The classroom is an archetypal venue, like the theatre or sports field. MOOC developers won't succeed by trying to replicate that venue. They have opportunities, however, to address participant needs that physical-world venues meet, such as awareness of classmates and a sense that the class is a timely event (as opposed to a tired old recording).
Blog: The end of civilization as we knew it
(by Aaron Marcus; http://interactions.acm.org/blog/view/the-end-of-civilization-as-we-knew-it)
But Aaron, you paid a lot of money for your MacBook Pro, doesn't that make you feel better about the experience?
Blog: What designers need to know/do to help transform healthcare
(by Richard Anderson; http://interactions.acm.org/blog/view/what-designers-need-to-know-do-to-help-transform-healthcare)
Well-stated! Reframing the problem doesn't happen nearly enough. In regard to your points about design research, how might you recommend adding more rigor for it to be appropriate enough? Is it spending more time in research, or focusing on the edge cases?
Blog Ai Weiwei, names, and memories (the background-foreground playground)
(by Deborah Tatar; http://interactions.acm.org/blog/view/ai-weiwei-names-and-memories-the-background-foreground-playground)
Great post! Leaves a lot to think about! It is interesting to me that in technology our names are treated like variables in programming. You can name your variable whatever you wantit is just used as a reference to get to the "meaning" or actual value. When we die, it is the equivalent of just deleting a user account. Just a bit flip. There are no technological tombstones or virtual ashes to scatter. Our "memories" don't live on with the websites that care about us; they are just cleared. (Well, except for the AARP in your father-in-law's case.)
Bravo from the author's dad!
©2013 ACM 1072-5220/13/07 $15.00
Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee.
The Digital Library is published by the Association for Computing Machinery. Copyright © 2013 ACM, Inc.
No Comments Found