Computing and people who work with computers are not the nerdy and negative images often portrayed in the media. As a computer scientist, educator and project evaluator with my hands and feet in many fields I live these realities every day. I am like the kid who never stops asking “why?” In this blog, I share my questions and curiosity about the interdisciplinary role of computing with a special concern for how computing can make the world a better place.
Showing posts with label creativity. Show all posts
Showing posts with label creativity. Show all posts
Thursday, June 6, 2013
What Does Awesome Product Mean?
What is the most awesome product you have ever encountered? Anything goes. I don't necessarily mean software or hardware or anything digital at all. If you believe it is a vacuum cleaner, great. Our instructions last night, as 50 of us lounged around the research labs at Intuit, were to form small groups and each present the most cool, fantastic, wonderful product we could think of. Then we were to pick the favorite of the lot. Next, small groups were to come together and report to the entire UX Speakeasy meetup on their findings.
Voices sometimes came out of the ceiling which was a bit disconcerting, but there was a logical explanation. We were too many to fit in one room so half of us were next door behind one way glass. From the observation room, half of us spied on (watched) the goings on of the other half, and contributed by speaking through the ceiling. From the front room all we could see was dark glass. Who knows what was really going on back there. The occasional thump against the glass gave no real clues.
Herding instinct tried to take over in the chosen products as most of the UX crowd chose mobile apps. Some of these apps were quite interesting, but I was somewhat disappointed that there wasn't more thinking outside the box. Nonetheless, there were a few fun surprises.
One member of my group loved his ancient music player. Dating from before the iPod, before iTunes, there was this little hand held device that did nothing but play music. It was called a Zune HD, made by Microsoft and definitely ancient (3-4 years old). Why was this device so awesome? Simplicity. All it did was play music. Period. No complicating phone or computer. And it was small. Unlike my monstrous Nexus 4, which I am having to regularly tell to STOP telling me things and sending me messages and notes and bings bongs and chirps. Once it took me three days to figure out why it kept randomly chirping at me and stop it.
Let's hear it for simplicity.
Then there was Air New Zealand. Air New Zealand received a loud round of "ooooohhh!!" and "ahhhhhh!!!" from the audience as we watched this nifty web site where you can put in how much money you have to spend and in return you get nifty displays showing how far you can go. Almost slipping under the radar, it caught my attention when the guy introducing the site to us said "All of our team had mobile apps. I went old school and brought my laptop. It paid off. I won".
(What does this have to say about the power of originality and standing out from the crowd?)
Perhaps my overall favorite of the evening came after the formal presentations. Someone showed me an app (yes, a mobile app) that measured your heart rate. Sounds ho hum until you play with it. You put your finger over the camera and a light shines out on your skin. The phone starts taking a reading and displays a live graph of your heart rate. The fun came when I challenged the device by holding my breath, jumping up and down, and engaging in deep and noisy heavy breathing. Not all at the same time.
Holding my breath confused it at first. The little graph quivered on a plateau for several seconds. Otherwise I managed to move my heart rate from the low 60s to close to 100 fairly easily.
I really wanted to take the phone away and sit in a corner and meditate for a while to see what would happen but other people wanted to play with it too.
On a more serious note, several members of the meetup organizing committee went out of their way to wear different shoes last night, in order to demonstrate that they had variety in their wardrobe. This in response to one of my previous posts where I took note of fashion choices among the attendees. I present the shoes - if you were at the event or know the committee members, can you identify them from their footwear?
Thursday, October 11, 2012
Sketching in the Computing Classroom
Once convinced by Sketchcamp San Diego that what you draw is good enough and that you should sketch anything and everything, the next adventure is deciding where sketching fits in your professional world. Thus, it was only a matter of time before I would explore how sketching could apply directly to computer science.
I could (but won't) write a treatise on all the opportunities for the professional computer scientist to sketch. Instead, let's ponder computing education.
Instructors, consider this - why not incorporate sketching into your classroom presentations? We know that humans are very visual creatures, but that doesn't mean that all visual presentations are good presentations (Death By Powerpoint comes to mind). Why not sketch part of your lecture as you give it, especially if you present in a large impersonal lecture hall? Take a look at my previous post for an example of this in action.
Unless you are working out a formal proof, I put it to you that there are plenty of opportunities to draw instead of write on the whiteboard, blackboard, tablet. You have to work out the details, but if you are creative enough to come up with other classroom innovations, as are many of my colleagues in the computer science education world, then you are up to the challenge of adding sketching to your pedagogical portfolio.
No, wait. Let me take back part of that last point. I'd love to see someone work out how to sketch a formal proof. Not only would it be terribly exciting but it would rock many people's world. Just think of the positive effect you could possibly have on those students who currently struggle with the abstraction of proofs.
Then there are the possibilities for collaborative sketching for software engineering students. The yawns and complaints (and subsequent below standard results) with which countless students approach the requirements gathering and specification development process are legendary. Not only do they miss the point, they can be disengaged, and just plain old lousy at client interaction. It takes practice, after all, to be a good listener and communicator.
What about reinventing the "Reqs and Specs" process to include team problem solving with the users present? Applying sketching techniques already used in the professional world, students can iterate on data interpretation and problem identification. Together they will produce a graphic illustration that captures the evolving conversation. What a great opportunity to break down barriers, achieve consensus and clarify intention. I suspect the sketching approach to specification development would suck in students and their client users alike.
I could (but won't) write a treatise on all the opportunities for the professional computer scientist to sketch. Instead, let's ponder computing education.
Instructors, consider this - why not incorporate sketching into your classroom presentations? We know that humans are very visual creatures, but that doesn't mean that all visual presentations are good presentations (Death By Powerpoint comes to mind). Why not sketch part of your lecture as you give it, especially if you present in a large impersonal lecture hall? Take a look at my previous post for an example of this in action.
Unless you are working out a formal proof, I put it to you that there are plenty of opportunities to draw instead of write on the whiteboard, blackboard, tablet. You have to work out the details, but if you are creative enough to come up with other classroom innovations, as are many of my colleagues in the computer science education world, then you are up to the challenge of adding sketching to your pedagogical portfolio.
No, wait. Let me take back part of that last point. I'd love to see someone work out how to sketch a formal proof. Not only would it be terribly exciting but it would rock many people's world. Just think of the positive effect you could possibly have on those students who currently struggle with the abstraction of proofs.
Then there are the possibilities for collaborative sketching for software engineering students. The yawns and complaints (and subsequent below standard results) with which countless students approach the requirements gathering and specification development process are legendary. Not only do they miss the point, they can be disengaged, and just plain old lousy at client interaction. It takes practice, after all, to be a good listener and communicator.
What about reinventing the "Reqs and Specs" process to include team problem solving with the users present? Applying sketching techniques already used in the professional world, students can iterate on data interpretation and problem identification. Together they will produce a graphic illustration that captures the evolving conversation. What a great opportunity to break down barriers, achieve consensus and clarify intention. I suspect the sketching approach to specification development would suck in students and their client users alike.
Labels:
Collaborative Learning,
computing education,
creativity,
design,
interdisciplinary computing,
user experience
Friday, October 5, 2012
Thinking Crazy - Do It!
"So much of coming up with great ideas is allowing yourself to think crazy" spoken by someone in the film "Design & Thinking" which screened last night at the Museum of Photographic Arts in San Diego. But can the corporate world accept this idea on a widespread basis? Can it be done without busting budgets? Important questions, addressed both directly and indirectly throughout this interesting film.
The film opened with scenes from the Occupy Movement and spent the next hour and fifteen minutes roving back and forth between New York City, San Francisco and Toronto, speaking with and observing a diverse and eclectic group of people in the design movement. I'm not sure why I'm calling it a movement, but after watching these people passionately describe what they do and what they think about the term Design Thinking, "movement" seems fitting.
There was the PhD candidate in Biology who had never heard of the term but described how he designs experiments with frogs (it seemed that no harm comes to the frogs - at least I hope so) and evolves his work through an iterative process that might sound familiar to someone from a classical design background. When he described the process of needing to be flexible and creative, it sounded rather like the many conversations during the film with people affiliated with classical design schools. These designers also spoke about following their intuition and being willing to shift course when development of a product produced unexpected feedback and results.
Moving from scientists to artists, along with CEOs, CTOs, and university faculty, one of the emerging themes in the film was: learning to be comfortable with taking risks. Realizing that you can do so at low cost. Taking risks and being willing to fail doesn't necessitate a huge budget. One of the challenges addressed throughout this film, both directly and indirectly, was how to "get a place at the table", i.e. in a number crunching bottom line world that wants algorithms for achieving success, how do you get the message across to all the relevant decision makers?
It can be done and the film showcased some wonderful examples. I loved the segment when the founder of Code For America was interviewed (was she was in her pajamas?) and spoke about the fear public officials have of putting anything up online that isn't "perfect". She made the very good point that the reason public officials are so risk averse is because we, the voting public, have made them afraid to make even the smallest mistake. No wonder they are afraid to innovate and experiment in the same way as firms in Silicon Valley. The good news however, is that organizations like Code For America are fostering cultural change in small incremental steps.
There is a lot more to say about the film's point of view on multi-disciplinarity, social entrepreneurship and having an impact. For now, consider how this might apply in your world:
"So much of coming up with great ideas is allowing yourself to think crazy"
Labels:
biology,
business,
communication,
creativity,
design,
industry issues,
interdisciplinary computing
Saturday, July 28, 2012
Quelque Chose est Différente Ici
It is healthy to periodically have your perspective altered as mine has been for the past few days here in France. When I go to sign on to this blog for example, I am asked for my "Adresse électronique" and my "Mot de passe" and depending upon whose computer I'm using I may find myself reminding my fingers that the "z" is not where I think it should be. Along with many other keys. It's not a QWERTY keyboard. Have you assumed that QWERTY is universal? Nope, it's not.
I checked out a definition on Wiktionnaire and then logged in to Facebook. "Bienvenue sur Facebook. Connectez-vous inscrive-vous ou décrouve!" Connect, write, or discover!
Another meaning for découvrir is "to take the lid off". Now that makes me think of food. Pas problèm, as so much of it is so good here. Pqss the pqstries: qnd the cheese: I wonder if the people at Facebook were trying some subtle way to appeal to the French palate. Not that Facebook is known for subtlety.
A French relative once told me that the best cheese is the most odiferous cheese; the way to identify the best cheeses, he said, were to sit them out and wait for a passing fly. If the fly passes above the cheese and drops dead the cheese is first rate. Yum. We immediately went cheese hunting.
A few days ago someone asked me to look over a document written in English and edit it for the grammar. They handed me a flash drive. Not any ordinary flash drive - not a bit of plastic in it. It is made of wood and remains closed by virtue of a magnet. Talk about ecologically ingenious. I've got to hand it to whoever created this device because I'd love to see us reduce the amount of environmentally toxic plastic used in our computing systems.
Electronic devices are some of the worst plastic offenders. This little flash drive is a reminder that there are alternatives to our near complete dependence on plastic if only we get creative in our thinking. Maybe a laptop made of wood isn't the solution (might it catch on fire when the drive heats up?) but surely there is something we can do about all that plastic.
You know what I haven't seen here in Paris? iPods. I can't recall having seen more than one or two people in Paris with those dangling ear cords. Smartphones are everywhere, everyone seems to have one, but there are signs in many places asking people not to use their phones and people respond by not using their phones! I think it's great. People aren't absorbed in their own isolated electronic worlds the way they often are in the US. They talk to in person to one another, to their children, to their friends.
Bonne journée
Another meaning for découvrir is "to take the lid off". Now that makes me think of food. Pas problèm, as so much of it is so good here. Pqss the pqstries: qnd the cheese: I wonder if the people at Facebook were trying some subtle way to appeal to the French palate. Not that Facebook is known for subtlety.
A French relative once told me that the best cheese is the most odiferous cheese; the way to identify the best cheeses, he said, were to sit them out and wait for a passing fly. If the fly passes above the cheese and drops dead the cheese is first rate. Yum. We immediately went cheese hunting.
A few days ago someone asked me to look over a document written in English and edit it for the grammar. They handed me a flash drive. Not any ordinary flash drive - not a bit of plastic in it. It is made of wood and remains closed by virtue of a magnet. Talk about ecologically ingenious. I've got to hand it to whoever created this device because I'd love to see us reduce the amount of environmentally toxic plastic used in our computing systems.
Electronic devices are some of the worst plastic offenders. This little flash drive is a reminder that there are alternatives to our near complete dependence on plastic if only we get creative in our thinking. Maybe a laptop made of wood isn't the solution (might it catch on fire when the drive heats up?) but surely there is something we can do about all that plastic.
You know what I haven't seen here in Paris? iPods. I can't recall having seen more than one or two people in Paris with those dangling ear cords. Smartphones are everywhere, everyone seems to have one, but there are signs in many places asking people not to use their phones and people respond by not using their phones! I think it's great. People aren't absorbed in their own isolated electronic worlds the way they often are in the US. They talk to in person to one another, to their children, to their friends.
Bonne journée
Tuesday, July 17, 2012
Photography Unites the Inner Artiste and Logician
I have the feeling that I am mentally rehashing a conversation that has been had for millenia in one form or another and for around 100 years in photography circles.
It concerns the latest step forward in technological capability. I read an article* recently about advances that permit such things as taking a picture and only deciding later where to place the focus or range of exposure. Simply put, the idea is that enormous amounts of digital data are captured and stored, including data about variables not previously captured such as angle and direction of light falling on an object all across the visual field. Later, you process the picture, picking and choosing which data to emphasize or remove entirely.
The implication is that, like cropping before it, this post-processing allows you to make an aesthetically pleasing picture out of a poorly composed snapshot. My inner artiste goes "HARUMPH".
Distracting the artiste momentarily with a new set of wallpaper choices, my inner logician takes the opportunity to jump in: "Hold on there...There are uses for this sort of approach, because not all photography is planned and carefully executed art."
For example, if, as the article states, you are a journalist and don't have time to sit around positioning everything, or the action is going by in a split second and you want to capture it live, great. Get those shots of the street war and get the heck out of the line of fire as fast as possible. Don't worry about getting back to relative safety only to discover all your shots are blurred or overexposed beyond recognition.
Or, lets' say you are a scientist looking for something and you aren't quite sure what or where it is, but it is in there somewhere... What a wonderful opportunity to dig around with the image to see what is hiding in there. My inner artiste and inner logician agree on the wonderfulness of the opportunity.
A wonderful combination of hardware and software makes it all possible. Algorithms that enable manipulation of incredibly dense numbers of pixels, working in tandem with some pretty sophisticated hardware in the "smart" lenses. Lenses that don't weigh a ton and require giant tripods or manual stabilizers that might as well be tripods. Speaking of which, "lens" singular may soon be the case - no more swapping out of lenses all the time. I'd really like to see that change in my camera pack. It would leave far more room for other things in my backpack as I trudge up the side of that mountain. Things like the rocks I like to collect.
The tradeoff is that by necessity, there will be even more people out there who miss the opportunity to really look at what is in front of them before they take a shot. The opportunity to be in the moment with your camera by virtue of having to observe, contemplate, study, see what comes to your inner self before you take that shot. The less technology there is in the camera, the more you have to pay attention to what you are looking at if you want something that is more than just not chopping off your friend's head (although we now have technology to user-proof against head chopping. It's called facial tracking software). One of the nice things about photography technology that doesn't attempt to do it all for you is that you are more likely to engage with your subject. Hopefully. Accidental decapitation existed 50 years ago, so maybe my position doesn't hold water.
I lug my camera everywhere and I suppose I will always plot plan and study what I'm shooting no matter what nifty geeky technology they come up with. And I'm no Luddite - I carry a nice (somewhat heavy) digital camera and lenses around with me. And I sometimes play with Photoshop just to see what comes of it. Just as I used to play in the darkroom. I love a good abstraction as much as a "realistic" (as much as there can be said to be realism) portrait or landscape.
When I started writing this post, I was kind of unhappy with the idea that soon cameras will allow me to blur, blunder and mess up my photographs and escape the consequences of not paying proper attention.
However, now I have come to the conclusion that the more the better because I can set everything on Manual mode if I want, I can enlist my camera ever more to the cause of investigative science and I can take that shot of the interesting passersby as well.
*"Smarter Photography" by Gary Anthes, Communications of the ACM June 2012 Vol 55, No. 6 pp 16-18
It concerns the latest step forward in technological capability. I read an article* recently about advances that permit such things as taking a picture and only deciding later where to place the focus or range of exposure. Simply put, the idea is that enormous amounts of digital data are captured and stored, including data about variables not previously captured such as angle and direction of light falling on an object all across the visual field. Later, you process the picture, picking and choosing which data to emphasize or remove entirely.
Distracting the artiste momentarily with a new set of wallpaper choices, my inner logician takes the opportunity to jump in: "Hold on there...There are uses for this sort of approach, because not all photography is planned and carefully executed art."
For example, if, as the article states, you are a journalist and don't have time to sit around positioning everything, or the action is going by in a split second and you want to capture it live, great. Get those shots of the street war and get the heck out of the line of fire as fast as possible. Don't worry about getting back to relative safety only to discover all your shots are blurred or overexposed beyond recognition.
A wonderful combination of hardware and software makes it all possible. Algorithms that enable manipulation of incredibly dense numbers of pixels, working in tandem with some pretty sophisticated hardware in the "smart" lenses. Lenses that don't weigh a ton and require giant tripods or manual stabilizers that might as well be tripods. Speaking of which, "lens" singular may soon be the case - no more swapping out of lenses all the time. I'd really like to see that change in my camera pack. It would leave far more room for other things in my backpack as I trudge up the side of that mountain. Things like the rocks I like to collect.
The tradeoff is that by necessity, there will be even more people out there who miss the opportunity to really look at what is in front of them before they take a shot. The opportunity to be in the moment with your camera by virtue of having to observe, contemplate, study, see what comes to your inner self before you take that shot. The less technology there is in the camera, the more you have to pay attention to what you are looking at if you want something that is more than just not chopping off your friend's head (although we now have technology to user-proof against head chopping. It's called facial tracking software). One of the nice things about photography technology that doesn't attempt to do it all for you is that you are more likely to engage with your subject. Hopefully. Accidental decapitation existed 50 years ago, so maybe my position doesn't hold water.
I lug my camera everywhere and I suppose I will always plot plan and study what I'm shooting no matter what nifty geeky technology they come up with. And I'm no Luddite - I carry a nice (somewhat heavy) digital camera and lenses around with me. And I sometimes play with Photoshop just to see what comes of it. Just as I used to play in the darkroom. I love a good abstraction as much as a "realistic" (as much as there can be said to be realism) portrait or landscape.
When I started writing this post, I was kind of unhappy with the idea that soon cameras will allow me to blur, blunder and mess up my photographs and escape the consequences of not paying proper attention.
However, now I have come to the conclusion that the more the better because I can set everything on Manual mode if I want, I can enlist my camera ever more to the cause of investigative science and I can take that shot of the interesting passersby as well.
*"Smarter Photography" by Gary Anthes, Communications of the ACM June 2012 Vol 55, No. 6 pp 16-18
Labels:
art,
creativity,
interdisciplinary computing,
technology
Saturday, March 3, 2012
SIGCSE 2012 - Hal Abelson, CS2013 Social and Professional Issues and More
Official registration at SIGCSE is 1278 as of Friday (yesterday) morning when we listened to Hal Abelson give the day's keynote talk. A very impassioned talk. Hal spoke at length about computers as instruments of intellectual empowerment. Computational Thinking -> Computational Values -> Computational Actions and the importance of generative platforms. A generative platform in this context is a platform (tool, application, etc) which can get used for something the people who created it had not thought of or planned for. A pedagogical tool, idea or lecture, a set of research results leads you or I to run in a different direction and produce something exciting for the classroom, for the community, for the academy (for anyone). Hal claimed that a war is underway for the soul of the university - there is a danger that the university is becoming more a marketplace for intellectual property and less a place for open sharing of intellectual ideas. (What does your experience tell you? Do you agree or disagree?)
As evidence, Hal provided impressive examples, such as copyright restrictions being placed upon faculty when they publish research results, such that they no longer own or can share their own research. He also shared a quote by one university general counsel (a large research university) stating that note taking in the classroom could constitute copyright infringement of faculty intellectual property; the suggestion was then made that faculty hand out a license agreement for students to sign at the beginning of the term.Wrap your head around that one if you can. Hal's talk was full of thought provoking information like this.
I visited the poster on display by the faculty group working on the Social and Professional Issues section of the new computing curricular guidelines (CS2013). Carol Spradling, Beth Hawthorne and Flo Appel and I had a fascinating conversation about what topics are generating the most discussion in the community - should they be part of the computing curriculum? Professional Communication is apparently a hot area. Some people believe it is critical and others believe it should not be included at all. In case you are curious, we are talking about (and now I quote from the draft document):
Also suggested:
What do you think - should these topics have a place in the computer science curriculum?
As evidence, Hal provided impressive examples, such as copyright restrictions being placed upon faculty when they publish research results, such that they no longer own or can share their own research. He also shared a quote by one university general counsel (a large research university) stating that note taking in the classroom could constitute copyright infringement of faculty intellectual property; the suggestion was then made that faculty hand out a license agreement for students to sign at the beginning of the term.Wrap your head around that one if you can. Hal's talk was full of thought provoking information like this.
I visited the poster on display by the faculty group working on the Social and Professional Issues section of the new computing curricular guidelines (CS2013). Carol Spradling, Beth Hawthorne and Flo Appel and I had a fascinating conversation about what topics are generating the most discussion in the community - should they be part of the computing curriculum? Professional Communication is apparently a hot area. Some people believe it is critical and others believe it should not be included at all. In case you are curious, we are talking about (and now I quote from the draft document):
- reading/understanding/summarizing technical material
- source code and documentation
- writing effective technical documentation
- dynamics of oral, written, and electronic team and group communication
- communicating professionally with stakeholders
- utilizing collaboration tools.
Also suggested:
- dealing with cross-cultural environment
- tradeoffs of competing risks in software projects, such as technology, structure/process, quality, people, market and financial
What do you think - should these topics have a place in the computer science curriculum?
Labels:
computing education,
creativity,
curriculum development,
interdisciplinary computing,
research,
writing
Wednesday, January 25, 2012
Computer Aided Composition & Hallucinations
The term "algorithmic composition" is loaded with baggage. Although the phrase pops up in our conversation fairly often, because of the loaded nature of the words, Alexis Kirke prefers "Computer Aided Composition" to describe the process he uses to compose music.
Although perfectly capable of coding, and having done so in the past, Alexis now prefers to work collaboratively with a professional programmer so that he can focus on the overall composition. "Programming is a creative act in itself" and it is all too easy to get sucked into it, he explains. Listening to Alexis describe how he is developing Insight, I couldn't help but think of a Vulcan Mind Meld. Alexis desires to "share the unsharable" - his consciousness, internal feelings, his Palinopsia hallucinations. (See the previous post for more on Alexis and how Palinopsia inspired this particular body of work)
According to the current plan, if you are in the audience at the February 10th performance you will see Alexis standing on stage behind a music stand holding an iPad. Perhaps he will be holding a pen. A Macintosh laptop is within arm's reach. The programmer sits in the front row of seats, and there is a flute player somewhere on stage with his own computer monitor. Alexis sees you; he also sees lighting designed to trigger his hallucinations.
It is difficult to formulate words to describe what this application program will probably look like, but I'm going to give it a whirl. The iPad will show Alexis a camera image of what he is seeing at any moment, an "augmented reality". The software on the iPad will incorporate parameters that correspond to common elements of Alexis' hallucinations. As Alexis experiences hallucinations, he will activate afterimage functionality and trigger an afterimage on the iPad. (At this point, a poor video connection on our Skype call produced a well timed "trail" as Alexis moved his hand across my line of sight). When this happens he is presented with visual options, filters and parameters. These are produced in partial response to an iterative feedback loop between himself and the programmer: he selects, via multi-touch, tapping, double tapping, 3 fingered presses, which parameters are appropriate and what filters to apply. For example, he can adjust the iPad screen brightness to correspond to his perception of brightness. He can likewise adjust screen size, the specific pattern of an afterimage, the rate of visual decay, single or multiple images, random patterns, and many other aspects of the visual echo. Alexis is simultaneously saying "yes, that" "no, not that" to presented options, and creating from scratch on the fly what he sees. He has to make the iPad "see" what he sees.
All this is happening extremely rapidly as his hallucinations develop, exist, and are replaced (sometimes in milliseconds) with the next hallucination. And we must not forget that this is not a completely free form activity - there will be at least 3 sections to the composition. Each section of the piece has different parameters. Alexis will reach over to the laptop to change sections. All of the visuals are handled by the iPad. When a hallucination is accurate, it is packaged up and sent wirelessly to the laptop, where the music resides. One reason for this division of labor is that the visual software is processor intensive. Memory optimization has been critical, and Alexis brought in someone who focused exclusively on iPad memory optimization.
Somehow, it all gets put together and coordinated: visual hallucinations from the iPad, musical scores from the laptop, contribution from a live flute player watching the iPad output.
You, sitting in the audience would see Alexis' hallucinations projected on a large screen, and hear his musical score to go along with it. All in 12 minutes.
The performance of Insight, at the Peninsula Arts Contemporary Music Festival, is going to be filmed. Let's hope it becomes available online!
Although perfectly capable of coding, and having done so in the past, Alexis now prefers to work collaboratively with a professional programmer so that he can focus on the overall composition. "Programming is a creative act in itself" and it is all too easy to get sucked into it, he explains. Listening to Alexis describe how he is developing Insight, I couldn't help but think of a Vulcan Mind Meld. Alexis desires to "share the unsharable" - his consciousness, internal feelings, his Palinopsia hallucinations. (See the previous post for more on Alexis and how Palinopsia inspired this particular body of work)
According to the current plan, if you are in the audience at the February 10th performance you will see Alexis standing on stage behind a music stand holding an iPad. Perhaps he will be holding a pen. A Macintosh laptop is within arm's reach. The programmer sits in the front row of seats, and there is a flute player somewhere on stage with his own computer monitor. Alexis sees you; he also sees lighting designed to trigger his hallucinations.
It is difficult to formulate words to describe what this application program will probably look like, but I'm going to give it a whirl. The iPad will show Alexis a camera image of what he is seeing at any moment, an "augmented reality". The software on the iPad will incorporate parameters that correspond to common elements of Alexis' hallucinations. As Alexis experiences hallucinations, he will activate afterimage functionality and trigger an afterimage on the iPad. (At this point, a poor video connection on our Skype call produced a well timed "trail" as Alexis moved his hand across my line of sight). When this happens he is presented with visual options, filters and parameters. These are produced in partial response to an iterative feedback loop between himself and the programmer: he selects, via multi-touch, tapping, double tapping, 3 fingered presses, which parameters are appropriate and what filters to apply. For example, he can adjust the iPad screen brightness to correspond to his perception of brightness. He can likewise adjust screen size, the specific pattern of an afterimage, the rate of visual decay, single or multiple images, random patterns, and many other aspects of the visual echo. Alexis is simultaneously saying "yes, that" "no, not that" to presented options, and creating from scratch on the fly what he sees. He has to make the iPad "see" what he sees.
All this is happening extremely rapidly as his hallucinations develop, exist, and are replaced (sometimes in milliseconds) with the next hallucination. And we must not forget that this is not a completely free form activity - there will be at least 3 sections to the composition. Each section of the piece has different parameters. Alexis will reach over to the laptop to change sections. All of the visuals are handled by the iPad. When a hallucination is accurate, it is packaged up and sent wirelessly to the laptop, where the music resides. One reason for this division of labor is that the visual software is processor intensive. Memory optimization has been critical, and Alexis brought in someone who focused exclusively on iPad memory optimization.
Somehow, it all gets put together and coordinated: visual hallucinations from the iPad, musical scores from the laptop, contribution from a live flute player watching the iPad output.
You, sitting in the audience would see Alexis' hallucinations projected on a large screen, and hear his musical score to go along with it. All in 12 minutes.
The performance of Insight, at the Peninsula Arts Contemporary Music Festival, is going to be filmed. Let's hope it becomes available online!
Labels:
art,
creativity,
innovation,
interdisciplinary computing,
music
Sunday, January 22, 2012
Computing...Music...Palinopsia
What would you do if, under the right circumstances, you saw hallucinations (no drugs involved)? If your name was Alexis Kirke you would take your two PhDs (one in arts, one in technology) and create a professional demonstration to share with the public.
I had no idea what to expect when, prior to our conversation, I read about Alexis and learned we were going to talk about his upcoming performance that would share live visual hallucinations. Who is this guy, I wondered?
Alexis Kirke is a member of Plymouth University's (UK) Interdisciplinary Centre for Computer Music Research, and Composer in Residence at the Plymouth Marine Institute. As part of his latter role, he has composed a score for a performance of "artificially intelligent whales" interacting with a saxophone. Impossible to describe; you just have to go here and expose yourself to it. Then there are other performances with titles such as: "Phrased and Confused" and "Drum Abuse". What next?
Afterimages. Ever look straight at a lightbulb and then been half blinded with the image of the bulb well after you stop looking at it? That is an afterimage. Afterimages come in two types, positive and negative. Positive afterimages are the same color as the original image and thought (according to my brief research) to have a neurological origin. An often cited example of positive afterimages are the "trails" associated with use of LSD. Conversely, negative afterimages invert the colors and are thought to have an optical/retinal origin.
Alexis has Palinopsia, a neurological condition that produces (most often positive) afterimages. What this means to Alexis is that when he is extremely tired, stressed, or in just the right lighting conditions, he will start to see afterimages. No drugs involved. He describes it as unnerving sometimes, but, he stresses, unlike schizophrenia there is never any question about what is real and what is a hallucination.
Most people with Palinopsia presumably find ways to work with and around the condition and there are resources out there to help such as The Palinopsia Foundation. Alexis, on the other hand, is going beyond co-existence. His first PhD was in the area of theoretical multi-robot systems and he spent time interacting with neuroscience research groups. After earning his degree, he worked in the fields of finance, and speech and sound recognition. Following a calling to move deeper into music, he then completed a second PhD in Computing Music and became a composer.
Composers work is performed; artists often take their inspiration from their own experiences. As I spoke to Alexis about the lead up to the creation of Insight, which will premier February 10 of this year, it no longer seemed bizarre to create a composition that uses computers to enable the sharing of visual hallucinations.
In the next post, I'll explain more about how it all works. Don't stray too far...
I had no idea what to expect when, prior to our conversation, I read about Alexis and learned we were going to talk about his upcoming performance that would share live visual hallucinations. Who is this guy, I wondered?
Alexis Kirke is a member of Plymouth University's (UK) Interdisciplinary Centre for Computer Music Research, and Composer in Residence at the Plymouth Marine Institute. As part of his latter role, he has composed a score for a performance of "artificially intelligent whales" interacting with a saxophone. Impossible to describe; you just have to go here and expose yourself to it. Then there are other performances with titles such as: "Phrased and Confused" and "Drum Abuse". What next?
Afterimages. Ever look straight at a lightbulb and then been half blinded with the image of the bulb well after you stop looking at it? That is an afterimage. Afterimages come in two types, positive and negative. Positive afterimages are the same color as the original image and thought (according to my brief research) to have a neurological origin. An often cited example of positive afterimages are the "trails" associated with use of LSD. Conversely, negative afterimages invert the colors and are thought to have an optical/retinal origin.
Alexis has Palinopsia, a neurological condition that produces (most often positive) afterimages. What this means to Alexis is that when he is extremely tired, stressed, or in just the right lighting conditions, he will start to see afterimages. No drugs involved. He describes it as unnerving sometimes, but, he stresses, unlike schizophrenia there is never any question about what is real and what is a hallucination.
Most people with Palinopsia presumably find ways to work with and around the condition and there are resources out there to help such as The Palinopsia Foundation. Alexis, on the other hand, is going beyond co-existence. His first PhD was in the area of theoretical multi-robot systems and he spent time interacting with neuroscience research groups. After earning his degree, he worked in the fields of finance, and speech and sound recognition. Following a calling to move deeper into music, he then completed a second PhD in Computing Music and became a composer.
Composers work is performed; artists often take their inspiration from their own experiences. As I spoke to Alexis about the lead up to the creation of Insight, which will premier February 10 of this year, it no longer seemed bizarre to create a composition that uses computers to enable the sharing of visual hallucinations.
In the next post, I'll explain more about how it all works. Don't stray too far...
Labels:
art,
creativity,
interdisciplinary computing,
music
Friday, January 6, 2012
Processing: Data Visualization and More
Today's meeting of the Processing workshop was as stimulating as yesterday's (see the post from yesterday). As before, the day was a blend of interactive instruction about Processing and hand's on time to code with the system. However, we went deeper - one of today's topics was data visualization using Processing. Check out these examples of linguistic poetry visualization by Ira Greenberg.
Here is an absolutely fascinating data visualization of Eurozone debt. Although I don't know if this is written in Processing or not, I have learned enough these past two days to tell you it would be fairly straightforward to do so.
Data visualization brings together the computer science and the generative art solidly. It isn't just about making pretty pictures. In order to create meaning and relevance in your visualization you need to manipulate, perhaps transform, your data. Depending upon the application, this could mean pulling in calculus, trigonometry, geometry, physics, and chemistry. It could mean creating well thought out OOP code, efficient threading and algorithmic selections, array manipulation, random number generation. Another one of the workshop leaders, Deepak Kumar, showed us a class assignment where students must use an array of Objects to create a row of streetlamps (any design they want) that randomly turn on and off.
We experimented with creating code that behaves like those art boards where you paint with water: as you draw lines/shapes with your mouse they fade behind you at whatever rate you dictate.
Web interfaces, network communication, digital audio generation. One of our workshop participants expressed an interest yesterday in working with sound in Processing - today we were listening to her computer broadcasting music from across the conference room.
If you are interested in using Processing in your classroom, the workshop leaders (Deepak Kumar, Dianna Xu, Ira Greenberg) would be happy to talk with you.
Here is an absolutely fascinating data visualization of Eurozone debt. Although I don't know if this is written in Processing or not, I have learned enough these past two days to tell you it would be fairly straightforward to do so.
Data visualization brings together the computer science and the generative art solidly. It isn't just about making pretty pictures. In order to create meaning and relevance in your visualization you need to manipulate, perhaps transform, your data. Depending upon the application, this could mean pulling in calculus, trigonometry, geometry, physics, and chemistry. It could mean creating well thought out OOP code, efficient threading and algorithmic selections, array manipulation, random number generation. Another one of the workshop leaders, Deepak Kumar, showed us a class assignment where students must use an array of Objects to create a row of streetlamps (any design they want) that randomly turn on and off.
We experimented with creating code that behaves like those art boards where you paint with water: as you draw lines/shapes with your mouse they fade behind you at whatever rate you dictate.
Web interfaces, network communication, digital audio generation. One of our workshop participants expressed an interest yesterday in working with sound in Processing - today we were listening to her computer broadcasting music from across the conference room.
If you are interested in using Processing in your classroom, the workshop leaders (Deepak Kumar, Dianna Xu, Ira Greenberg) would be happy to talk with you.
This little guy is expressing his excitement:
(click on him and then be patient for a moment or two)
Labels:
animation,
art,
computing education,
creativity,
generative art,
interdisciplinary computing,
visualization
Thursday, January 5, 2012
Computer Science via Generative Art and Vice Versa
Reporting this evening from Dallas (Texas) where I am attending a workshop about the Processing system, a unique way to learn programming concepts using generative art. Within 10 minutes of starting to use Processing, I was sucked completely into coding, and was producing animated abstractions. This was my first program (a lot more interesting than any Hello World):
About 12 of us were sitting around the conference table and we were all heads down, heads up (to look at the overhead display where one of the presenters was explaining various features), heads down, heads up, type type type. College and University faculty, high school teachers, computer scientists, digital designers. Type, type type.
Before I knew it we were not only coding in Java (a language I generally dislike with a passion) but trying to figure out how to make loops, swoops, and geometric patterns bounce around the screen. And bounce they did - or grow, shrink, grow-shrink-grow-shrink. Change colors, size, shapes, speed up, slow down, fade in, out, turn corners, move around smooth rollercoaster-like curves...the only boundary was our imagination. When was the last time your first day of class was that productive and absorbing?
And this is no toy system. Processing has some unique attributes. Not only does the system use a real language (Java), it is accessible (such an easy interface), it is powerful and it is fun. It is also open source, contains excellent online help, and there is an exhibition space for uploading your creations along with their code. As open source, you can download other people's creations and code as well.
Designed originally by people affiliated with the MIT Media Lab as a language for artists to explore coding as a medium, it is now becoming well known in the computer science education community. One of our workshop leaders, Ira Greenberg, is a painter by training; he downloaded an early version of Processing around 2001 and not long after wrote a book (the first ever I believe) "Processing - Creative Coding and Computational Art". Fast forward: Now Ira has a dual appointment in Computer Science and Engineering and in the Meadows School of the Arts at Southern Methodist University.
What you can't see from these pictures I created (before lunch) is that they are dynamic. Both pictures, especially the one on the right, were moving under the direction of my code. Now yes, I have a background in programming and teaching Java, but I have no particular expertise in graphics. And I really do despise Java. Such a pain ...Usually. Not today.
More to the point, the two creations of mine included here are far less sophisticated than what others in our group were creating; one participant, a public high school teacher, created a brilliant beautiful demo on recursion this afternoon. Someone else created what looked like an ever expanding universe of pulsating multi-shaped colored particles.
There were a lot of fried brains by the end of the day because people barely looked up - most were glued to their laptops straight through lunch. By the end of the day it clear that we were well on our way into sophisticated concepts in science, math and computing. It just seemed to ... happen. I can't wait for tomorrow.
About 12 of us were sitting around the conference table and we were all heads down, heads up (to look at the overhead display where one of the presenters was explaining various features), heads down, heads up, type type type. College and University faculty, high school teachers, computer scientists, digital designers. Type, type type.
Before I knew it we were not only coding in Java (a language I generally dislike with a passion) but trying to figure out how to make loops, swoops, and geometric patterns bounce around the screen. And bounce they did - or grow, shrink, grow-shrink-grow-shrink. Change colors, size, shapes, speed up, slow down, fade in, out, turn corners, move around smooth rollercoaster-like curves...the only boundary was our imagination. When was the last time your first day of class was that productive and absorbing?
And this is no toy system. Processing has some unique attributes. Not only does the system use a real language (Java), it is accessible (such an easy interface), it is powerful and it is fun. It is also open source, contains excellent online help, and there is an exhibition space for uploading your creations along with their code. As open source, you can download other people's creations and code as well.
Designed originally by people affiliated with the MIT Media Lab as a language for artists to explore coding as a medium, it is now becoming well known in the computer science education community. One of our workshop leaders, Ira Greenberg, is a painter by training; he downloaded an early version of Processing around 2001 and not long after wrote a book (the first ever I believe) "Processing - Creative Coding and Computational Art". Fast forward: Now Ira has a dual appointment in Computer Science and Engineering and in the Meadows School of the Arts at Southern Methodist University.
What you can't see from these pictures I created (before lunch) is that they are dynamic. Both pictures, especially the one on the right, were moving under the direction of my code. Now yes, I have a background in programming and teaching Java, but I have no particular expertise in graphics. And I really do despise Java. Such a pain ...Usually. Not today.
More to the point, the two creations of mine included here are far less sophisticated than what others in our group were creating; one participant, a public high school teacher, created a brilliant beautiful demo on recursion this afternoon. Someone else created what looked like an ever expanding universe of pulsating multi-shaped colored particles.
There were a lot of fried brains by the end of the day because people barely looked up - most were glued to their laptops straight through lunch. By the end of the day it clear that we were well on our way into sophisticated concepts in science, math and computing. It just seemed to ... happen. I can't wait for tomorrow.
Labels:
animation,
art,
computing education,
creativity,
generative art,
interdisciplinary computing
Friday, December 30, 2011
2012 Is Looking Good For Interdisciplinary Computing
All signs are that 2012 is going to be a banner year for interdisciplinary computing. You don't have to look far to see evidence that more and more people are actively engaging in and publicizing interdisciplinary computing work.
On the computing education front: At the upcoming SIGCSE 2012 conference there will be sessions on studio based learning (several), digital humanities, interdisciplinary database applications, knitting patterns and program tracing, science fiction in computer science education. There will be presentations on healthcare and computing (several), and interdisciplinary travel. There will also be a special session devoted to the role of interdisciplinary computing in academia, research and industry. This session will be run by Ursula Wolz and Boots Cassel, the same people who organized the interdisciplinary computing meetings I attended and wrote about this past year. Interdisciplinary is becoming a hot topic in computing education.
In the private sector: Volumes of online and print text are dissecting everything that might have led to Steve Jobs repeated successes. Analyses of Jobs and the innovations he drove have repeated his comments about how Apple existed at the intersection of liberal arts and technology. A repercussion of these discussions is going to be (I predict) even greater corporate emphasis on how a meeting of minds between computing and traditionally non-technical fields can lead to innovation.
The term "social intelligence" is becoming more common as we look at what we can learn, intuit, predict, and know from analyzing social media. If we are to really understand what social media has to tell us about people, or, conversely, if we are to really use social media intelligently for business purposes (two sides of the same coin), we will have to do more to integrate our understandings from psychology, anthropology and sociology into our computing development work. There is huge potential here for intelligent forward thinking collaborations.
Most telling: If you pick up any computing / technology magazine off the supermarket rack and flip through it, you will find advertisements from organizations that tout their interdisciplinary or multidisciplinary achievements. Energy, water, biomedical, transportation, communication, disaster prediction and management, interactive literature.
One can focus on the exaggeration and hype inherent to much advertising, but that would be missing the bigger picture. The important thing to note is that the whole notion of promoting interdisciplinary computing has entered the mainstream. When large and small organizations jockey to convince potential customers and clients that *they* are on the forefront of interdisciplinary computing, then interdisciplinary computing is no longer on the fringe. Funding follows, and smart funding has the potential to nurture environments that drive technological innovation.
People will make the final decisions and determine the directions interdisciplinary computing takes. I am optimistic and excited about where we can go..
On the computing education front: At the upcoming SIGCSE 2012 conference there will be sessions on studio based learning (several), digital humanities, interdisciplinary database applications, knitting patterns and program tracing, science fiction in computer science education. There will be presentations on healthcare and computing (several), and interdisciplinary travel. There will also be a special session devoted to the role of interdisciplinary computing in academia, research and industry. This session will be run by Ursula Wolz and Boots Cassel, the same people who organized the interdisciplinary computing meetings I attended and wrote about this past year. Interdisciplinary is becoming a hot topic in computing education.
In the private sector: Volumes of online and print text are dissecting everything that might have led to Steve Jobs repeated successes. Analyses of Jobs and the innovations he drove have repeated his comments about how Apple existed at the intersection of liberal arts and technology. A repercussion of these discussions is going to be (I predict) even greater corporate emphasis on how a meeting of minds between computing and traditionally non-technical fields can lead to innovation.
The term "social intelligence" is becoming more common as we look at what we can learn, intuit, predict, and know from analyzing social media. If we are to really understand what social media has to tell us about people, or, conversely, if we are to really use social media intelligently for business purposes (two sides of the same coin), we will have to do more to integrate our understandings from psychology, anthropology and sociology into our computing development work. There is huge potential here for intelligent forward thinking collaborations.
Most telling: If you pick up any computing / technology magazine off the supermarket rack and flip through it, you will find advertisements from organizations that tout their interdisciplinary or multidisciplinary achievements. Energy, water, biomedical, transportation, communication, disaster prediction and management, interactive literature.
One can focus on the exaggeration and hype inherent to much advertising, but that would be missing the bigger picture. The important thing to note is that the whole notion of promoting interdisciplinary computing has entered the mainstream. When large and small organizations jockey to convince potential customers and clients that *they* are on the forefront of interdisciplinary computing, then interdisciplinary computing is no longer on the fringe. Funding follows, and smart funding has the potential to nurture environments that drive technological innovation.
People will make the final decisions and determine the directions interdisciplinary computing takes. I am optimistic and excited about where we can go..
Happy Healthy Interdisciplinary New Year!
Labels:
computing education,
creativity,
innovation,
interdisciplinary computing,
professional issues
Monday, November 21, 2011
The Computer Sand Society
This week begins the holiday season for many people and often with it, unfortunately, way too much stress. Maybe that is why this week (Thanksgiving week in the US) brings out some strangeness. There was the blog post forwarded by a friend about stuffing a turkey with twinkies. It is hard not to feel fondness for something that springs back into shape when you step on it, but ... make a meat glaze out of the so-called "creme filling"? Yuck.
I also received an advertisement in the mail addressed to me at "The Computer Sand Society". Walking back from the mailbox, I thought: this could be a new interdisciplinary application! In response to this inspiration, a friend sent a lovely video link about sand animation; another friend suggested that, nice as it sounds, poolside would be much better than beachside because sand is hard on laptops. Could it be worse than three bouts of sick video cards? Perhaps, yes it could. Although I once told a cell carrier that my phone had mysteriously died when it had in fact fallen in the toilet (would you want to explain that one?), I'm not sure the computer manufacturer would buy into the notion that a gritty substance floating around the motherboard stemmed from disintegrating integrated circuits.
However, as I do believe in the power of creative thinking to spur innovation, I suspect there is opportunity for The Computer Sand Society to come into its own.
Modeling and simulation of sand castles. Has anyone developed a system, similar to those used by architectural design firms, to analyze the possibilities for ever more complex creations, factoring in the properties of sand - fineness of particles, distribution of various well crumbled crustacean shells, positioning relative to the high tide mark, mineral components?
Sand castle building is serious business for some people. The U.S. Open Sandcastle Competition bit the dust this year and its demise has many people very upset. I wonder if profits from my envisioned application might have helped hold it together? We could have perhaps drawn on the nearby expertise of the famous Scripps Institution of Oceanography, NOAA (the National Oceanographic and Atmospheric Administration) and the local surfers who are out every morning, afternoon and evening rain or shine, 365 days a year. Who understands the interactions between sand and surf better than these subject matter experts?
I have always wanted to combine my love of the outdoors with the potential of computing. A typo by some overworked marketing employee has given me the inspiration for a new hi-tech startup. All that is needed now is a really dedicated team to get it off its feet - and an angel investor.
Any takers?
Happy Thanksgiving - have some fun and forget the stressful stuff for a few days.
I also received an advertisement in the mail addressed to me at "The Computer Sand Society". Walking back from the mailbox, I thought: this could be a new interdisciplinary application! In response to this inspiration, a friend sent a lovely video link about sand animation; another friend suggested that, nice as it sounds, poolside would be much better than beachside because sand is hard on laptops. Could it be worse than three bouts of sick video cards? Perhaps, yes it could. Although I once told a cell carrier that my phone had mysteriously died when it had in fact fallen in the toilet (would you want to explain that one?), I'm not sure the computer manufacturer would buy into the notion that a gritty substance floating around the motherboard stemmed from disintegrating integrated circuits.
However, as I do believe in the power of creative thinking to spur innovation, I suspect there is opportunity for The Computer Sand Society to come into its own.
Modeling and simulation of sand castles. Has anyone developed a system, similar to those used by architectural design firms, to analyze the possibilities for ever more complex creations, factoring in the properties of sand - fineness of particles, distribution of various well crumbled crustacean shells, positioning relative to the high tide mark, mineral components?
Sand castle building is serious business for some people. The U.S. Open Sandcastle Competition bit the dust this year and its demise has many people very upset. I wonder if profits from my envisioned application might have helped hold it together? We could have perhaps drawn on the nearby expertise of the famous Scripps Institution of Oceanography, NOAA (the National Oceanographic and Atmospheric Administration) and the local surfers who are out every morning, afternoon and evening rain or shine, 365 days a year. Who understands the interactions between sand and surf better than these subject matter experts?
I have always wanted to combine my love of the outdoors with the potential of computing. A typo by some overworked marketing employee has given me the inspiration for a new hi-tech startup. All that is needed now is a really dedicated team to get it off its feet - and an angel investor.
Any takers?
Happy Thanksgiving - have some fun and forget the stressful stuff for a few days.
Labels:
artwork,
business,
creativity,
Earth Science,
innovation,
interdisciplinary computing,
twinkies
Saturday, November 5, 2011
Interdisciplinary Computing Meeting 3: Day 2
My computer screen is still on an acid trip - perhaps more so. Tonight it is purple and orange with green swirls and oozing deep amoeba-like dripping drooling things. But the keys work, so I can continue to talk about the meeting. The same caveats apply as yesterday, about typos, lack of links and copy editing. My notes from today are doubly challenged as I not only took them half blind but am now reading them back to myself more blind. However, I consider this an interesting cognitive challenge.
Onwards.
We started the morning with a faculty panel that seeded a discussion of challenges to Interdisciplinary Computing (IC) as well as interesting experiences. One particularly interesting speaker was Teresa Nakra from the Music Department at The College of New Jersey. She conducted an opera as part of her early music studies and later went to the MIT media lab where she worked with Rosalind Picard (of Affective Computing fame) on digital opera. Teresa spoke about designing a jacket for the conductor to wear which took readings of a variety of activities that were going on during the performance of the opera. Teresa spoke about the interdisciplinary nature of opera, which is probably not something many people in computing think of. This subject matter rang some bells for me, as one of my undergraduate degrees was in Drama, which field led me indirectly into the computing field. At that time everything was analog (certainly not the case now) but there were these interesting engineers in the lighting booth and one thing led to another and...
We spoke in more depth today about the various constituencies that are involved in the success or failure of IC and discussed ways to engage with them and foster a climate conducive to IC. A particularly interesting question came up:
Would it be preferable, in an ideal world, to have a greater preponderance of dual (or multi) subject matter experts or to have a greater number of computing professionals who are fluent enough in another field to hold serious conversations in that (those) field(s) without being a SME (pronounced "SMEE")?
We as a group had varied views on the matter and this led to a very productive discussion of the implications of each. What do you think? What scenario would be better for the fostering and ongoing success of Interdisciplinary Computing?
In another breakout session that I sat in on we discussed obstacles faced by industry. Interestingly enough, one of the topics that came out without my initiating it, was the very interdisciplinary nature of UX work in industry - short for User Experience if you aren't familiar with the term. Interesting to me, because I have been working on UX , and have written about UX a few times in this blog. It is clearly an interdisciplinary area of work - computing, psychology, art, design, development - depending upon one's emphasis, these and other disciplines can be central. UX is a clear point of connection between academic interdisciplinary computing work and industry. Much of Computer Science Education research work can or does fall under the UX umbrella.
In discussing the challenges faced by industry it became clear that there is no universal set of challenges and it is hard to make any generalizations that stick. Large companies may have more time to allow people to come up to speed and may have time and resources for some cross training; small companies may have to get something delivered yesterday. Traditional hi-tech companies may have one set of IC needs whereas the health care IT industry may have a vastly different set of requirements (must one have medical background? someone suggested this might well be the case). Non-profits, for-profit companies - different types of missions, thus different challenges. These discussions also led to a brief conversation about how to prepare students in very concrete ways - such as providing advice on developing resumes. Does one want to be a generalist or a specialist within the IC world? If one is working in an IC area, in other words, to what extent should one narrowly niche and to what extent should one be broad? These questions relate back to the question about whether it would be preferable to have dual SMEs or single area SMEs with a solid working knowledge in other areas.
So you see, we were beginning to pick up on patterns of issues that have to be carefully considered and addressed (and we did have discussions on these subjects). I wish I had room to delve deeply into it, but there will eventually be a formal report from the organizers of these meetings (Ursula Wolz and Boots Cassel) and some of the ideas I mention will no doubt be part of the discussion there.
Another theme that came up again and again, yesterday and today, was the need for communication strategies among people who are involved in IC. Support mechanisms to facilitate communication, formal (workshops, meetings, regional structures to support ongoing conversations) and informal (funded lunches as one idea. A little pizza can go a long way), in-service activities specifically targeted at IC collaborations, mentoring opportunities to bring in and support new colleagues.
Publicity, outreach, and awareness raising came up a lot today. If we are to affect Hearts, Minds and Culture, (a phrase from yesterday) then we must start putting the whole notion, appeal and benefits of Interdisciplinary Computing into people's minds in many different ways. If the general citizenry and youth perceive IC as interesting, and a part of the fabric of society, then we will go a long way towards achieving a major shift towards accomplishing many of the more discrete goals of IC.
This post was updated on 11/10/11 to fix typos and add links.
Onwards.
We started the morning with a faculty panel that seeded a discussion of challenges to Interdisciplinary Computing (IC) as well as interesting experiences. One particularly interesting speaker was Teresa Nakra from the Music Department at The College of New Jersey. She conducted an opera as part of her early music studies and later went to the MIT media lab where she worked with Rosalind Picard (of Affective Computing fame) on digital opera. Teresa spoke about designing a jacket for the conductor to wear which took readings of a variety of activities that were going on during the performance of the opera. Teresa spoke about the interdisciplinary nature of opera, which is probably not something many people in computing think of. This subject matter rang some bells for me, as one of my undergraduate degrees was in Drama, which field led me indirectly into the computing field. At that time everything was analog (certainly not the case now) but there were these interesting engineers in the lighting booth and one thing led to another and...
We spoke in more depth today about the various constituencies that are involved in the success or failure of IC and discussed ways to engage with them and foster a climate conducive to IC. A particularly interesting question came up:
Would it be preferable, in an ideal world, to have a greater preponderance of dual (or multi) subject matter experts or to have a greater number of computing professionals who are fluent enough in another field to hold serious conversations in that (those) field(s) without being a SME (pronounced "SMEE")?
We as a group had varied views on the matter and this led to a very productive discussion of the implications of each. What do you think? What scenario would be better for the fostering and ongoing success of Interdisciplinary Computing?
In another breakout session that I sat in on we discussed obstacles faced by industry. Interestingly enough, one of the topics that came out without my initiating it, was the very interdisciplinary nature of UX work in industry - short for User Experience if you aren't familiar with the term. Interesting to me, because I have been working on UX , and have written about UX a few times in this blog. It is clearly an interdisciplinary area of work - computing, psychology, art, design, development - depending upon one's emphasis, these and other disciplines can be central. UX is a clear point of connection between academic interdisciplinary computing work and industry. Much of Computer Science Education research work can or does fall under the UX umbrella.
In discussing the challenges faced by industry it became clear that there is no universal set of challenges and it is hard to make any generalizations that stick. Large companies may have more time to allow people to come up to speed and may have time and resources for some cross training; small companies may have to get something delivered yesterday. Traditional hi-tech companies may have one set of IC needs whereas the health care IT industry may have a vastly different set of requirements (must one have medical background? someone suggested this might well be the case). Non-profits, for-profit companies - different types of missions, thus different challenges. These discussions also led to a brief conversation about how to prepare students in very concrete ways - such as providing advice on developing resumes. Does one want to be a generalist or a specialist within the IC world? If one is working in an IC area, in other words, to what extent should one narrowly niche and to what extent should one be broad? These questions relate back to the question about whether it would be preferable to have dual SMEs or single area SMEs with a solid working knowledge in other areas.
So you see, we were beginning to pick up on patterns of issues that have to be carefully considered and addressed (and we did have discussions on these subjects). I wish I had room to delve deeply into it, but there will eventually be a formal report from the organizers of these meetings (Ursula Wolz and Boots Cassel) and some of the ideas I mention will no doubt be part of the discussion there.
Another theme that came up again and again, yesterday and today, was the need for communication strategies among people who are involved in IC. Support mechanisms to facilitate communication, formal (workshops, meetings, regional structures to support ongoing conversations) and informal (funded lunches as one idea. A little pizza can go a long way), in-service activities specifically targeted at IC collaborations, mentoring opportunities to bring in and support new colleagues.
Publicity, outreach, and awareness raising came up a lot today. If we are to affect Hearts, Minds and Culture, (a phrase from yesterday) then we must start putting the whole notion, appeal and benefits of Interdisciplinary Computing into people's minds in many different ways. If the general citizenry and youth perceive IC as interesting, and a part of the fabric of society, then we will go a long way towards achieving a major shift towards accomplishing many of the more discrete goals of IC.
Along these lines, I will conclude this once again longish post (and one that is killing my eyes!) with another amusing moment from today. Someone brought up the information that when the original Chuck E Cheese was developed it incorporated a model of exposing entire families to the "product" and thus gaining buy-in from families, and that, get this, Chuck E Cheese was THE premier place for showcasing technology to children through robotics. A member of our group personally remembered this. According to one perspective, the robotic approach didn't quite work out because it scared children (oops).
However, overall the "engage the entire family" model was successful and has continued, spreading to many other companies. Some highly creative soul in our group suggested "CyberCheese" as a name for an Interdisciplinary Computing marketing campaign. Engage the entire family in computational interaction. If the entire family is engaged, parents, kids, extended family, friends - things could take off.
After I about died laughing at the name, I realized...hey...this idea isn't so bad is it?
This post was updated on 11/10/11 to fix typos and add links.
Labels:
community,
computing education,
creativity,
industry issues,
interdisciplinary computing,
making connections,
professional issues
Thursday, September 22, 2011
Commonalities Among Computing Professionals Who Work for Good
I am performing a final review of the the production text of my book on socially beneficial uses of computing (officially: Computers and Society: Computing For Good). The computing topics range all across the discipline of computer science (high performance computing to social media) and the non-computing topics are as diverse as saving endangered sea turtles, medical informatics and educational software for children with disabilities. Several years in the writing, I met on this journey either virtually or in person, dozens and dozens of people. Looking back on all these wonderful encounters I am struck once again by the commonalities among them.
1. Passion. More than anything else, the people who shared their stories (and those of their organizations) with me felt that their work was more than a job. Again and again I heard about how the cause they worked towards (earthquake prediction, identifying best practices recommendations for infant care, poverty alleviation) gave a sense of purpose above and beyond a paycheck. When things got tough, their passion for helping people or the environment supported them.
2. Risk Takers. As many books on innovation in business have documented, a willingness to take risks, experience setbacks or even failures, is absolutely necessary. Some people I met had abandoned secure positions to follow their dreams, or within their current careers they strategically stuck their necks out to convince others that their ideas were sound and worthy of support. Again and again. Technically and non-technically. Risk taking, dealing with the inevitable setbacks by getting up and moving forward are an ingrained trait in many of the people who are doing the greatest good with computing.
3. Curious and Open Minded. A common reaction to being a risk taker (whether in the world of computing innovation or elsewhere) is to face and go beyond those who say "it can't be done" or "this is not the time". In fact, as the interdisciplinary computing pioneers I met demonstrated, you need to let these critiques roll off. Instead, keep asking questions, gathering information and recognize there is rarely only one way to solve a problem. In fact, the more that conventional wisdom says this is so, the less likely it is to be true.
4. Keep Technically Current and Constantly Learn. Just as I had the privilege and necessity of diving deep into the world of mobile devices, computer security and other areas of computing, the people who are highly effective and innovative with their socially beneficial projects are continuously studying. Not necessarily (or usually) through formal education, but through reading, experimenting, sharing, and just plain digging into material further than they "had to".
Perhaps more than anything else, the computing and non-computing professionals knew themselves well, and knew what their dreams were. They made a personal commitment to pursue those dreams.
If you are reading this, it is likely you have a desire to "do good" with computing. Do you know what your dreams are and are you pursuing them?
1. Passion. More than anything else, the people who shared their stories (and those of their organizations) with me felt that their work was more than a job. Again and again I heard about how the cause they worked towards (earthquake prediction, identifying best practices recommendations for infant care, poverty alleviation) gave a sense of purpose above and beyond a paycheck. When things got tough, their passion for helping people or the environment supported them.
2. Risk Takers. As many books on innovation in business have documented, a willingness to take risks, experience setbacks or even failures, is absolutely necessary. Some people I met had abandoned secure positions to follow their dreams, or within their current careers they strategically stuck their necks out to convince others that their ideas were sound and worthy of support. Again and again. Technically and non-technically. Risk taking, dealing with the inevitable setbacks by getting up and moving forward are an ingrained trait in many of the people who are doing the greatest good with computing.
3. Curious and Open Minded. A common reaction to being a risk taker (whether in the world of computing innovation or elsewhere) is to face and go beyond those who say "it can't be done" or "this is not the time". In fact, as the interdisciplinary computing pioneers I met demonstrated, you need to let these critiques roll off. Instead, keep asking questions, gathering information and recognize there is rarely only one way to solve a problem. In fact, the more that conventional wisdom says this is so, the less likely it is to be true.
4. Keep Technically Current and Constantly Learn. Just as I had the privilege and necessity of diving deep into the world of mobile devices, computer security and other areas of computing, the people who are highly effective and innovative with their socially beneficial projects are continuously studying. Not necessarily (or usually) through formal education, but through reading, experimenting, sharing, and just plain digging into material further than they "had to".
Perhaps more than anything else, the computing and non-computing professionals knew themselves well, and knew what their dreams were. They made a personal commitment to pursue those dreams.
If you are reading this, it is likely you have a desire to "do good" with computing. Do you know what your dreams are and are you pursuing them?
Friday, September 2, 2011
Fun and Weird For Friday
It's Friday, it is the start of a holiday weekend in the US, so I thought I'd share some fun things I found. Way back in the Dark Ages when robots first hit the commercial scene I was entranced by a review of one home robot that had a built-in set of sensors to detect life forms. The robot had a limited speech capability to make it friendly. The early models had some slight glitches; apparently one robot snuggled up to a toilet bowl (the size and shape somehow registered as sentient) and talked to it. Another robot used a heat sensor to get just a little too close to the fireplace, again thinking it was alive. But oh, I wanted one.
We have come a long way. I have eyed a Roomba, not necessarily because I need a robot vacuum cleaner but because I wanted to watch it interact with my cat. But now, things have gotten even better. Check these out:
RoboKing Triple Eye vacuum cleaner - it can spy on people, scope for dirt and you can control it via Smart Phone when you are stuck in a traffic jam and are bored to tears breathing exhaust fumes.
Bakebot: Plans for a robot to cook for you...this one needs some work before it goes commercial. I happen to prefer to be my own mad scientist in the kitchen. Especially while this device is still in the oven.
Play Rock Paper Scissors against a computer. You can play against a Novice or a Veteran. Then you can read what the computer is thinking. You will get sucked right into this one...really. When I played against a novice computer my results were: Win, Win, Tie, Lose, Tie, Tie. When I played against a veteran, my results were: Lose, Lose, Tie, Lose, Lose. The computer performed a complex seeming analysis of what I was thinking and then told me what 20,000 (or so) other people did that was similar to my strategy . When I played the Novice, I was actually trying to outwit it. When I played the Veteran I just decided to randomly wing it and it was quite engaging to see how the computer analyzed my winging strategy. You see...you can get sucked in. Look how much I wrote about Rock Paper Scissors! So if you have no plans for the evening...
I really dislike mushrooms but I had a lovely time growing little yellow mushrooms with Mushroom Life and listening to them go "eep" "eep" "eep"; the faster I clicked the faster went the "eeps" and the faster the little yellow things popped up on the grid. More smiles on your face.
You can play Mushroom Life seriously of course. But after the spy vacuum, the half-baked robot cook, and doing battle with the computer over RPS, it seems fitting to work on making music out of popping mushrooms.
Have a nice weekend ("eep").
We have come a long way. I have eyed a Roomba, not necessarily because I need a robot vacuum cleaner but because I wanted to watch it interact with my cat. But now, things have gotten even better. Check these out:
RoboKing Triple Eye vacuum cleaner - it can spy on people, scope for dirt and you can control it via Smart Phone when you are stuck in a traffic jam and are bored to tears breathing exhaust fumes.
Bakebot: Plans for a robot to cook for you...this one needs some work before it goes commercial. I happen to prefer to be my own mad scientist in the kitchen. Especially while this device is still in the oven.
Play Rock Paper Scissors against a computer. You can play against a Novice or a Veteran. Then you can read what the computer is thinking. You will get sucked right into this one...really. When I played against a novice computer my results were: Win, Win, Tie, Lose, Tie, Tie. When I played against a veteran, my results were: Lose, Lose, Tie, Lose, Lose. The computer performed a complex seeming analysis of what I was thinking and then told me what 20,000 (or so) other people did that was similar to my strategy . When I played the Novice, I was actually trying to outwit it. When I played the Veteran I just decided to randomly wing it and it was quite engaging to see how the computer analyzed my winging strategy. You see...you can get sucked in. Look how much I wrote about Rock Paper Scissors! So if you have no plans for the evening...
I really dislike mushrooms but I had a lovely time growing little yellow mushrooms with Mushroom Life and listening to them go "eep" "eep" "eep"; the faster I clicked the faster went the "eeps" and the faster the little yellow things popped up on the grid. More smiles on your face.
You can play Mushroom Life seriously of course. But after the spy vacuum, the half-baked robot cook, and doing battle with the computer over RPS, it seems fitting to work on making music out of popping mushrooms.
Have a nice weekend ("eep").
Thursday, August 25, 2011
Things to Think With: Crochet Hyperbolic Planes and Computing
Do you sew? Knit? Weave? Crochet? Personally, I have rarely ventured beyond replacing buttons on shirts, but Sarah Kuhn, Professor in the Psychology Department at the University of Massachusetts Lowell, taught herself to crochet after being inspired to create hyperbolic planes by Daina Taimina's book "Crocheting Adventures with Hyperbolic Planes".
Sarah has been working for years at the intersection of art, sociology, computing and engineering education. This latest project is part of a new research area, part of her evolving investigation of ways to bring mathematics and computational concepts to life. When she first saw some of these crocheted hyperbolic planes she asked herself: are they more than models? Can these objects be used to discover things? To her, that is a key point for a successful learning environment.
The answer is yes. Creating a hyperbolic plane crochet 'object' (the best word I can think of, although it feels insufficient) provides opportunities to explore algorithms, patterns, emergent properties, and programming - for starters. How?
I asked Sarah to explain how it all works, and asked her to assume she was speaking to a completely clueless crocheter (as I am, having never even touched a pair of needles). She patiently stepped me through the "single crochet stitch", the basic stitch in crochet. She explained the ways this stitch can be used, with no other more complex stitches, to create an object such as the gray spherical object pictured above or the colorful object below. The process is indeed algorithmic. You start with a circle out of yarn and move outwards in a spiral one stitch at a time. There is also something called "increasing". I won't try to replicate the explanation for fear of completely butchering it, but suffice it to say, every creation is different because of variables (computing concept!) including how often you increase, the type of yarn, the quality of the yarn, the color, and the composition of the yarn.
Crochet hyperbolic planes provide a simple entry into the worlds of mathematics, computing, and analytical thinking in general. They are easy to make, fun, and small changes result in sometimes surprising outcomes. A little crochet tweak here and you have a different form of ruffle; another crochet tweak and the shape shifts. Another topic: Design patterns and the implementation decisions they lead to.
Highly portable, crochet hyperbolic planes are excellent conversation starters. Sarah summarizes a typical conversation:
Scene: The doctor's office. Personae Dramatae: Sarah in chair, Person Nearby in chair (perhaps bored).
Person Nearby: "What is that?"
Sarah: "This is a hyperbolic plane"
Person: "What's that?"
Sarah: "It is math"
Person: "Really? That's math! If someone had presented that to me as math in high school I would have liked it".
[Conversation continues....]
Voila. An aesthetic entrance into the world of the formerly abstract. More complex concepts wait to be tackled by progressing to a discussion of weaving; weaving has far greater complexity than crochet and an interesting history that we know includes the computational (ahem...Jacquard Loom?).
Fiber arts (which encompass sewing, knitting, weaving, crochet) cross cultural, age, geographic and social boundaries. In some societies they are associated with women's activities, in other societies with men's activities. As Sarah says "a STEM opportunity hiding in plain sight". Not surprisingly, she is developing several ambitious project ideas that will integrate fiber arts into a variety of classes and programs with the explicit goal of encouraging interest in STEM disciplines - computing included.
Sign me up. I wanted to reach out and grab one of these crocheted hyperbolic planes the moment I saw their pictures. Wouldn't it be fascinating and fun to explore the world of computing while creating one's own personal weird masterpieces of yarn? Stepping stones to complexity. Sarah Kuhn is demonstrating that the arts and computing have a lot in common.
Sarah has been working for years at the intersection of art, sociology, computing and engineering education. This latest project is part of a new research area, part of her evolving investigation of ways to bring mathematics and computational concepts to life. When she first saw some of these crocheted hyperbolic planes she asked herself: are they more than models? Can these objects be used to discover things? To her, that is a key point for a successful learning environment.
The answer is yes. Creating a hyperbolic plane crochet 'object' (the best word I can think of, although it feels insufficient) provides opportunities to explore algorithms, patterns, emergent properties, and programming - for starters. How?
I asked Sarah to explain how it all works, and asked her to assume she was speaking to a completely clueless crocheter (as I am, having never even touched a pair of needles). She patiently stepped me through the "single crochet stitch", the basic stitch in crochet. She explained the ways this stitch can be used, with no other more complex stitches, to create an object such as the gray spherical object pictured above or the colorful object below. The process is indeed algorithmic. You start with a circle out of yarn and move outwards in a spiral one stitch at a time. There is also something called "increasing". I won't try to replicate the explanation for fear of completely butchering it, but suffice it to say, every creation is different because of variables (computing concept!) including how often you increase, the type of yarn, the quality of the yarn, the color, and the composition of the yarn.
Crochet hyperbolic planes provide a simple entry into the worlds of mathematics, computing, and analytical thinking in general. They are easy to make, fun, and small changes result in sometimes surprising outcomes. A little crochet tweak here and you have a different form of ruffle; another crochet tweak and the shape shifts. Another topic: Design patterns and the implementation decisions they lead to.
Highly portable, crochet hyperbolic planes are excellent conversation starters. Sarah summarizes a typical conversation:
Scene: The doctor's office. Personae Dramatae: Sarah in chair, Person Nearby in chair (perhaps bored).
Person Nearby: "What is that?"
Sarah: "This is a hyperbolic plane"
Person: "What's that?"
Sarah: "It is math"
Person: "Really? That's math! If someone had presented that to me as math in high school I would have liked it".
[Conversation continues....]
Voila. An aesthetic entrance into the world of the formerly abstract. More complex concepts wait to be tackled by progressing to a discussion of weaving; weaving has far greater complexity than crochet and an interesting history that we know includes the computational (ahem...Jacquard Loom?).
Fiber arts (which encompass sewing, knitting, weaving, crochet) cross cultural, age, geographic and social boundaries. In some societies they are associated with women's activities, in other societies with men's activities. As Sarah says "a STEM opportunity hiding in plain sight". Not surprisingly, she is developing several ambitious project ideas that will integrate fiber arts into a variety of classes and programs with the explicit goal of encouraging interest in STEM disciplines - computing included.
Sign me up. I wanted to reach out and grab one of these crocheted hyperbolic planes the moment I saw their pictures. Wouldn't it be fascinating and fun to explore the world of computing while creating one's own personal weird masterpieces of yarn? Stepping stones to complexity. Sarah Kuhn is demonstrating that the arts and computing have a lot in common.
Labels:
algorithms,
artwork,
computing education,
creativity,
Fiber Arts,
Fine Arts,
interdisciplinary computing
Sunday, July 24, 2011
A Tale of Two Valuations: Academia Next
I initially thought this post would be a piece of cake compared to the previous post about the corporate perspective. Not so. Perhaps because of my extensive academic experience I am far more aware of the variance of how professionals are valued in the world of higher education. So I have been looking for points of common ground within academia...I am almost afraid someone will throw a rotten tomato at me because I know too much (I've been reading a murder mystery, where the person who knows too much often comes to a messy end).
To state the obvious (to academics at least) there are the three classic areas of valuation for faculty: Teaching, Research and Service. Service (pretty much anything not teaching or research related such as committee work, performing outreach or being a student adviser) can safely be said to come last in the pile. Do no committee work and you will get dinged; do too much and you will get dinged (I know someone who was denied tenure because he was told he performed too much service work). So the trick is to find the middle ground according to the culture of your department and institution.
From there is gets murkier.
Teaching: In some institutions this is virtually all that counts. But how it is measured varies widely. In some cases, it is all about teaching evaluations. Period. Get those numbers up and get them high or else. The pressure can be intense, and in extreme examples there can be a completely predictable desperation to "please" students above all else. In my experience, this is not the norm, and is incredibly destructive to the learning process. More often, in a teaching oriented institution, evaluations are important, but only one indicator of how a faculty is evaluated. More sophisticated methods of assessing effective learning are used. And by effective I'm not talking statistical evaluation; I'm talking qualitative evaluations. That is healthy imo. Institutions with a well rounded process for evaluating teaching can produce amazing students who go on to do amazing things inside and outside the classroom and after graduation. And the faculty feels professionally successful and appreciated.
Research: In some institutions this is virtually all that counts. Again, the worst case scenario is where not only are publications counted (literally) but the venues for publication are ranked. If you don't get into "the top" pubs, forget it. You are toast. Even within computing, there are disagreements as to what counts as a quality publication venue. Then there are grants. Worst case scenario, you need a fixed number of grants and big dollars - millions would be nice. Not healthy, as there is only so much money to go around and that sets up a system of guaranteed winners and losers regardless of quality. Very much like using a normalization curve in grading. Something I never used and never will because it has all sorts of negative side effects that many educators are well enough aware of that I won't repeat them here.
Quite a bit of gloom up in those paragraphs. Now to inject a positive perspective. BALANCE. It is all about balance. The original idea behind Teaching, Research and Service was to promote balance. Some of all three are needed from every faculty. Many institutions, although they do by design weight teaching and research differently, maintain a healthy balance. What are the factors that indicate successful teaching in such situations? Each professional is evaluated in the context of both institutional need and known pedagogical / cognitive learning understandings. Other factors come into play to varying degrees depending upon the context: local needs, student needs, etc. What are the factors that indicate successful research? Very similar actually. The institutional needs and established understandings of rigor in scientific research lead to an evaluation of individual contributions (reminder here that we are talking computing and related areas. I can't speak to areas such as the arts and humanities). Grants in these institutions aren't just about how much money is brought in, but about the effect the work is likely to have on science, or in the case of educational research such as computer science education research on the discovery and dissemination of improved teaching and learning theory and application.
It feels like I've short circuited my comments, but that comes from knowing too much.
A summation might be: for faculty in academia professional valuation is based on teaching, research and service, and in a healthy environment there is a contextually appropriate and healthy balance. Value is not just numbers, nor is it vague and undefinable.
I feel like I'm stating the obvious, but that is only the case if you are an academic reading this. Based upon some of the comments I received to my last post about valuation in the corporate world, there are many to whom this post will be news.
One of my next tasks will be to see where I can locate opportunities for common ground.
But first, I'll ask you to graciously do what you did before, and provide your perspective on:
1) What can you add about how academics in higher education are judged to provide value to their organizations? What can you add that is concrete - i.e. can be said in very concise form?
2) Where do you see common ground between between corporate and academic valuation of professional contribution to their organizations?
(I think we have all heard about the areas where there is supposedly no common ground. Let's look for the positive now).
To state the obvious (to academics at least) there are the three classic areas of valuation for faculty: Teaching, Research and Service. Service (pretty much anything not teaching or research related such as committee work, performing outreach or being a student adviser) can safely be said to come last in the pile. Do no committee work and you will get dinged; do too much and you will get dinged (I know someone who was denied tenure because he was told he performed too much service work). So the trick is to find the middle ground according to the culture of your department and institution.
From there is gets murkier.
Teaching: In some institutions this is virtually all that counts. But how it is measured varies widely. In some cases, it is all about teaching evaluations. Period. Get those numbers up and get them high or else. The pressure can be intense, and in extreme examples there can be a completely predictable desperation to "please" students above all else. In my experience, this is not the norm, and is incredibly destructive to the learning process. More often, in a teaching oriented institution, evaluations are important, but only one indicator of how a faculty is evaluated. More sophisticated methods of assessing effective learning are used. And by effective I'm not talking statistical evaluation; I'm talking qualitative evaluations. That is healthy imo. Institutions with a well rounded process for evaluating teaching can produce amazing students who go on to do amazing things inside and outside the classroom and after graduation. And the faculty feels professionally successful and appreciated.
Research: In some institutions this is virtually all that counts. Again, the worst case scenario is where not only are publications counted (literally) but the venues for publication are ranked. If you don't get into "the top" pubs, forget it. You are toast. Even within computing, there are disagreements as to what counts as a quality publication venue. Then there are grants. Worst case scenario, you need a fixed number of grants and big dollars - millions would be nice. Not healthy, as there is only so much money to go around and that sets up a system of guaranteed winners and losers regardless of quality. Very much like using a normalization curve in grading. Something I never used and never will because it has all sorts of negative side effects that many educators are well enough aware of that I won't repeat them here.
Quite a bit of gloom up in those paragraphs. Now to inject a positive perspective. BALANCE. It is all about balance. The original idea behind Teaching, Research and Service was to promote balance. Some of all three are needed from every faculty. Many institutions, although they do by design weight teaching and research differently, maintain a healthy balance. What are the factors that indicate successful teaching in such situations? Each professional is evaluated in the context of both institutional need and known pedagogical / cognitive learning understandings. Other factors come into play to varying degrees depending upon the context: local needs, student needs, etc. What are the factors that indicate successful research? Very similar actually. The institutional needs and established understandings of rigor in scientific research lead to an evaluation of individual contributions (reminder here that we are talking computing and related areas. I can't speak to areas such as the arts and humanities). Grants in these institutions aren't just about how much money is brought in, but about the effect the work is likely to have on science, or in the case of educational research such as computer science education research on the discovery and dissemination of improved teaching and learning theory and application.
It feels like I've short circuited my comments, but that comes from knowing too much.
A summation might be: for faculty in academia professional valuation is based on teaching, research and service, and in a healthy environment there is a contextually appropriate and healthy balance. Value is not just numbers, nor is it vague and undefinable.
I feel like I'm stating the obvious, but that is only the case if you are an academic reading this. Based upon some of the comments I received to my last post about valuation in the corporate world, there are many to whom this post will be news.
One of my next tasks will be to see where I can locate opportunities for common ground.
But first, I'll ask you to graciously do what you did before, and provide your perspective on:
1) What can you add about how academics in higher education are judged to provide value to their organizations? What can you add that is concrete - i.e. can be said in very concise form?
2) Where do you see common ground between between corporate and academic valuation of professional contribution to their organizations?
(I think we have all heard about the areas where there is supposedly no common ground. Let's look for the positive now).
Sunday, July 17, 2011
A Tale of Two Valuations: Hi-tech Corporations First
Sometimes you have to hit a problem head on and just lay it out there. I've been thinking about the best way to discuss some of what I've been hearing and learning on and offline, in public and private communications, as I tackle this question of corporate and academic valuation of a professional's contribution. As I stated earlier, I believe there is more in common than may appear on the surface, but as I discuss this topic with people, I am not yet finding the concrete information I want to ferret out. I'm not ready by a long shot to give up. We need this information to be able to bridge the cultural divides and learn from each other. So I have been debating how to get away from the more abstract and/or philosophical discussions and into the reality of day to day existence.
I am going to write some of what I have heard and do it from two angles. First from a corporate angle, and second, from an academic angle. And both, I might add, based also upon my experience in both arenas.
First, perhaps the more challenging for me: the corporate angle. Although I have worked in the hi-tech world, more of my career has been in academia. Let's stick to the realm of hi-tech and management level positions - here you are likely to find more interdisciplinary activity, however defined, and innovative companies recognize that. Here goes...
I have been told that, from an American corporate perspective, a person is valued primarily on their monetary contributions. Irregardless of where they are coming from (professionally). To be more precise, here is a close paraphrase of what someone said to me:
"you have to show quantitatively how much $$$ you have brought the organization; you have to show how much $$$ you saved the organization; you have to show the resources (physical) you obtained for the organization. That is what they expect. That is what they want to see. That is what they care about. That is what matters".
Is that IT?
Is that ALL?
Is that REALLY the only thing that counts or the thing that weighs far heavier than anything else?
Is it a fact that no matter what else one may have accomplished, that if one can't show precise fiscal contributions one is not highly valued?
This question is burning at me when I look at the question of professional value from the corporate angle. If the answer is yes, I'm feeling rather uneasy. The implications for bridging a cultural divide with academia become more daunting (but still not impossible my optimistic side says).
So let me put it out there to those of you in corporate hi-tech, especially if you have held or currently hold, a management level position of any sort.
Do you agree with the above statements about how you and your peers are valued? If you agree, are you ok with this or how are you trying to change it? If you do not agree, or if there is more to it, then what else in your experience really counts?
I am going to write some of what I have heard and do it from two angles. First from a corporate angle, and second, from an academic angle. And both, I might add, based also upon my experience in both arenas.
First, perhaps the more challenging for me: the corporate angle. Although I have worked in the hi-tech world, more of my career has been in academia. Let's stick to the realm of hi-tech and management level positions - here you are likely to find more interdisciplinary activity, however defined, and innovative companies recognize that. Here goes...
I have been told that, from an American corporate perspective, a person is valued primarily on their monetary contributions. Irregardless of where they are coming from (professionally). To be more precise, here is a close paraphrase of what someone said to me:
"you have to show quantitatively how much $$$ you have brought the organization; you have to show how much $$$ you saved the organization; you have to show the resources (physical) you obtained for the organization. That is what they expect. That is what they want to see. That is what they care about. That is what matters".
Is that IT?
Is that ALL?
Is that REALLY the only thing that counts or the thing that weighs far heavier than anything else?
Is it a fact that no matter what else one may have accomplished, that if one can't show precise fiscal contributions one is not highly valued?
This question is burning at me when I look at the question of professional value from the corporate angle. If the answer is yes, I'm feeling rather uneasy. The implications for bridging a cultural divide with academia become more daunting (but still not impossible my optimistic side says).
So let me put it out there to those of you in corporate hi-tech, especially if you have held or currently hold, a management level position of any sort.
Do you agree with the above statements about how you and your peers are valued? If you agree, are you ok with this or how are you trying to change it? If you do not agree, or if there is more to it, then what else in your experience really counts?
Labels:
business,
creativity,
industry issues,
innovation,
professional issues
Sunday, July 10, 2011
Random Weekend Thoughts About Creative Computer Use
I'm going to lay off the super serious stuff this evening as I have a little list of "items" ripe for a creative computer scientist to evaluate.
- A GPS system might have been useful for the small child I saw this afternoon on the beach who was happily walking about a mile away from his parents. My friend followed the toddler, who was totally unconcerned, and with the aid of a lifeguard got him back to his mother. Her only comment about how far away her kid had wandered on the packed beach was an unconcerned "there are a lot of people around". Who do you think most needs the GPS system? a) the child b) the mother c) the lifeguard d) all of the above e) none of the above ?
- I have jury duty next week and San Diego Mass Transit's software connection to Google Maps is determined to route me to either Tijuana Mexico, Monterrey Mexico, or Paraguay. Where do you think the problem lies? (I truly believe I will not be crossing the international border tomorrow, regardless of what the software system insists)
- A friend was very concerned about the fact that software was not being used to more efficiently assist in food redistribution to the homeless. He described in great detail what such software would look like and asked why no one had created it. I realized as he spoke that the software to do what he says does exist, but is used in other applications. Last week I spent a good hour with a visiting family member at the harbor watching a Dole (as in bananas and pineapples) tanker unload box after box of food and load them onto trucks off to destinations all over the western US. The plaque on the harbor walkway briefly described the complex distribution system used to get those bananas I eat every morning from Central America effectively and efficiently and in just the right state of green to all the places they have to go. What would it take to get such a system into the hands of large scale non profits doing essentially the same thing?
- While I am sitting in the stuffy courthouse waiting room (NOT in Paraguay) I am going to be on the lookout for just how computerization is or isn't being used...and how it could be. I might even get a bit inquisitive and ask questions. This would not be unusual behavior for me. As long as it doesn't result in my landing on the other side of the court system than was intended.
Labels:
business,
community,
creativity,
Social Issues in Computing
Thursday, June 30, 2011
Assessing Value in the Corporate and Academic Worlds: An Interdisciplinary Problem?
During all of these ponderings about innovation and interdisciplinary computing I have been working with the question of where interesting ideas coming from the corporate world can (should? do?) apply in the academic world. Sometimes the cross over seems quite reasonable with a little twist in thinking, as in this, a summative statement from The Innovator's Dilemma book (the past 5 or so posts, in case you haven't been following the conversation):
"...historically, disruptive technologies involve no new technologies - rather they consist of components built around proven technology (ies) and put together in a novel product architecture that offers a set of attributes never before available".
It only takes a few word changes to see how this applies to interdisciplinary computing. I bet you can figure it out if you have been following this conversation (can you?).
A larger question that looms over me now, is - just how far and in how many directions, can experiences of successful or unsuccessful processes in the business world be applied in academia? And conversely, what can the corporate world learn from successful and unsuccessful processes in academia?
On the one hand the cultures are vastly different. On the other hand, I am becoming convinced that there is a lot that can transfer from one to the other. Because my reading came from a book about the corporate world, I was looking at how the academic world sometimes fits the author's theories of successful "product" innovation.
I am equally curious about how understandings of success and failure in academia can be useful to corporate success.
There are a lot of hard questions when you start from scratch. I'll start with a very basic one: the concept of "value".
The corporate world often places value upon monetary contributions (Person X saved the corporation $Y by doing XYZ, or Person X brought in $Y dollars or Z physical resources to the corporation). Lately, I have been asking some professional acquaintances how they would place "value" upon academic contributions quantitatively.
I was not surprised by the reactions I have been receiving, which show just how differently "value" is determined in higher education and in corporate America. The more difficult I find it to try and bridge this cultural divide, (I'm starting to think of it as an interdisciplinary computing problem of a new sort) the more I want to do it.
How can the academic and corporate worlds arrive at a common understanding of value that does not involve one unilaterally imposing its "definitions" on the other?
How is VALUE going to be defined?
"...historically, disruptive technologies involve no new technologies - rather they consist of components built around proven technology (ies) and put together in a novel product architecture that offers a set of attributes never before available".
It only takes a few word changes to see how this applies to interdisciplinary computing. I bet you can figure it out if you have been following this conversation (can you?).
A larger question that looms over me now, is - just how far and in how many directions, can experiences of successful or unsuccessful processes in the business world be applied in academia? And conversely, what can the corporate world learn from successful and unsuccessful processes in academia?
On the one hand the cultures are vastly different. On the other hand, I am becoming convinced that there is a lot that can transfer from one to the other. Because my reading came from a book about the corporate world, I was looking at how the academic world sometimes fits the author's theories of successful "product" innovation.
I am equally curious about how understandings of success and failure in academia can be useful to corporate success.
There are a lot of hard questions when you start from scratch. I'll start with a very basic one: the concept of "value".
The corporate world often places value upon monetary contributions (Person X saved the corporation $Y by doing XYZ, or Person X brought in $Y dollars or Z physical resources to the corporation). Lately, I have been asking some professional acquaintances how they would place "value" upon academic contributions quantitatively.
I was not surprised by the reactions I have been receiving, which show just how differently "value" is determined in higher education and in corporate America. The more difficult I find it to try and bridge this cultural divide, (I'm starting to think of it as an interdisciplinary computing problem of a new sort) the more I want to do it.
How can the academic and corporate worlds arrive at a common understanding of value that does not involve one unilaterally imposing its "definitions" on the other?
How is VALUE going to be defined?
- If you are an academic and you had to express your "value" to a corporate executive in a way they would appreciate, what would you say?
- If you are in the corporate world and you had to find "value" in an academic's career in a way that acknowledged their worth honestly, what would you say?
Labels:
business,
contextualized,
creativity,
industry issues,
innovation,
interdisciplinary computing,
professional issues
Subscribe to:
Posts (Atom)






