Showing posts with label artwork. Show all posts
Showing posts with label artwork. Show all posts

Friday, July 25, 2014

Science Communication Team Building - with Paint. Seriously?

How do you tell a male or female scorpion?

The idea of having to sing in public or play an instrument made my stomach flip. I usually feel that sensation only when landing in the turbulence that seems to always surround the Dallas/Forth Worth airport. However, here I was, feet planted firmly on the Arizona sand, and that sick almost pukey sensation wouldn't go away. I didn't know anyone - how could I possibly say anything?

Along with 35 or so others, scientists and engineers, a philosopher, someone from theatre and several artists, I was newly arrived at the C.O.D. Ranch for  Sonoran SciComm. We were here to work on communication and team building and we had been warned (promised) that we'd be pushed outside our comfort zones. We all wanted to be there, some of us (ahem) having almost fallen all over ourselves at the opportunity. I think it safe to say everyone had a passion for the environment and was working one way or another for sustainability.

But at that moment I thought I might be ill. Try as I might I couldn't bring myself to choose the Music activity. The mere thought that I might suffer a panic attack in front of dozens of people I had never met before was intolerable. Ever since the summer after my Freshman year, when I had an ill fated on-stage encounter with Cole Porter's Anything Goes while working at a Lake George NY resort, I have preferred my singing take place at 75 mph with the windows rolled up. They said they were letting me go because I couldn't make hospital corners. True, I wasn't cut out to be a chambermaid, singing or otherwise.

So, 30 odd years later, back at SciComm, I opted for the Painting. A nice, reasonably solitary activity with which to get my feet under me. So I thought. A dozen of us stood ready to wield our instruments against the canvas: Let us at it!

Then they told us to give our tightly gripped (favorite) painting tool to our neighbor. Bummer. They teamed us up and let us loose with the acrylics. My new friend Liz and I hit it off immediately; she a marine biologist by training and me a fan of all things small and wiggly in the water. We happily created waves and little tadpoles and oceanic abstractions together.We negotiated each other's styles, learning about one another as we had a running conversation about our emerging masterpiece.  Perfect.

Until they told us to pause, move to the right and continue painting on someone else's canvas. But, but... ok, don't get attached to material things. I tried not to look (too often) at what was happening to our abandoned Work of Art. Instead, Liz and I discussed what to do with the canvas left to us (no doubt with an equal level of regret) by another team. We started off tentatively, trying not to change their vision. Whatever it was. Tippy toeing around the edges. Wider ranging discussions developed between the two of us as we not only figured out what to apply where (which by this point had started to include some artifacts stuck to the canvas), but tried to psych out what the whole exercise was really about.

As a result, we weren't particularly surprised when we were told to change canvases again. And then again. Eventually  it was IMPOSSIBLE not to "mess up" prior work. There simply wasn't that much untouched canvas on these easels. Our original work was by now unrecognizable. However, Liz and I had decided we weren't messing it up, they weren't messing it up, but that we were contributing to a group project.

It was only 10am. My attention span was starting to wander. This activity was supposed to continue until noon. I was feeling like I was done. DONE. I think Liz was having similar thoughts. I said something to one of our activity organizers. His polite but firm response was "You must continue!". It wasn't an order; in fact we had been explicitly told the evening before that nothing was mandatory and we didn't have to do anything we didn't want to, so no one would have said a word had I taken a break - and never come back.

I sucked it up. I had a little conversation with myself "I'm not going to sulk. I'm not going to slide out of the room". "As much as I want to go off somewhere and stare meditatively at a cactus, I'm not going to do so. That would mean abandoning the group" .

Yet I was feeling a tad irritable. My cognitive state told me one thing but my affective state was not cooperating. Liz had wandered off somewhere, also feeling a need for change and some time apart. It turned out she was doing something really nifty with the paint out on the porch, a la Andy Warhol, to a series of magazine pictures of stuffy old men .

For myself, I reasoned that no one had said we had to paint on the canvas, so I proceeded to pour long trails of blood and guts black and red down the side of a supply box. It was very satisfying. And you know,  after a while it started to look kinda nifty. Not long afterwards I was back with Liz, sharing the box desecration together and watching her deface the stuffy old men.

Things went on from there. We covered the box, and still an hour remained. So we picked up the paint bottles, threw aside the tools and proceeded to sling great blobs of drooling oozing highly satisfying paint all over the canvases. Other people joined in and soon many of us were smearing, swiping, pouring, and slithering paint all over the place. Attachments were Bye Bye. Interpersonal shyness was a thing of the past. Conversations were as fluid as the running paint.

In hindsight, I think that was the point. After three and a half hours, we had gone from being self conscious, protective of "our" art and ways of doing things, carefully negotiating perceptions of other people's preferences, to happily smearing paint every which way and learning to at the very least appreciate what each other was doing no matter what it looked like or how it got there.

The whole weekend was like that. In case we'd thought we were "done" after the morning's Painting, we were wrong. I never went within range of the musical group, but I did get a chance to scream at the top of my lungs during the Improv Session which was most cathartic.

So began Sonoron SciComm. So continued Sonoran SciComm. So... no, it isn't over. This wasn't just a solo weekend event but a community building activity among a bunch of people who might very well, perhaps now more than before, work together effectively on some very serious and important (and no doubt fun) science.

I'm not ready to belt out Stevie Nicks in public, but perhaps some day. Maybe. With a good team.


Thursday, December 6, 2012

UX Design, Classic Art and Grounded Theory

Lo and Behold: Art meets User Experience Design meets Grounded Theory. At a local brewery no less.

This month's meeting of the UX (User Experience) Speakeasy group featured Julie Morgan from Digitaria sharing a few design case studies using a tool called Optimal Workshop. Standing in front of a large tank, presumably full to the brim with fermenting beer, Julie enthusiastically popped up images of artwork ranging from Van Gogh to Gustav Klimt to Jasper Johns, with a Roman arch tossed in for good measure.

Each of these pieces of art was an analogy to something in the user design research process. A Klimt piece related to music, which related to patterns and the search for harmony in web design. An early version of Van Gogh's Potato Eaters was tied to UX sketching and a later version to the final online design. There was something about a Roman arch in there when discussing Information Architecture. I didn't catch everything she said about it, but now I'm thinking about how one little center stone at the top holds the whole thing up for centuries. Brilliant. It also connects two sides, as in the desire to bridge the gap between users and designers - one of Julie's main points last night.

You see, that is what made the classical art analogies so interesting - they got you thinking in new ways. Looking for connections and inspiration from old to new.

Such as when Grounded Theory popped into my head. As Julie was explaining the different ways a technique called Card Sorting works, and how it can be done with Open or Closed categories, I knew I had heard this before. In Grounded Theory (a well established form of Qualitative Research methodology dating from the 1960s) you can observe people in their natural setting and see what patterns emerge, what categories or activities appear, and eventually develop a behavioral hypothesis from it. This would be a purist form of Grounded Theory. Very much like a UX Designer providing users a stack of cards with labels on them about something they care about, and watching what happens as they discuss them and sort them into categories of their choosing.

Alternatively,with Closed category Card Sorting you can test a user experience hypothesis about something (e.g. "they think this way about web design XYZ...and will behave this way...") using predetermined categories. Use the same cards as in the Open approach, and watch what happens as the users try to put the cards in your categories. Maybe all will go as predicted. Maybe it won't and they push back in some way. Oops, hypothesis not true, users hate this design. Very much like going into a Grounded Theory study with a hypothesis about user behavior, seeing what happens and adjusting codes, taxonomies and theories accordingly.

Inspiration takes place in all phases of these monthly meetings. Somehow, after the formal presentation, while discussing the relationship between art, design and how the commercial world works, I found myself in a deep and meaningful conversation about how to outwit Wireless providers (yes, those organizations that provide service for your mobile phone). There is art and skill to legally outsmarting those guys. Perhaps this reflects the desire to move from Edvard Munch's "The Scream" towards Monet's "The Magpie".


Friday, July 6, 2012

Sculpting Code to Create and Retain the Art

I read in passing the comment "what if software maintenance was taught the way sculpture is taught". To my dismay nothing more was said in the article about how this might occur. I turned to my friends and colleagues and asked for memories on the pedagogy of teaching sculpture. One person responded "pedagogically? WTH?" which reminded me that not *all* of my acquaintances understand educator-speak. After rephrasing the question to let the confused know that what I wanted was recollections of teaching strategies in a sculpture class, the responses came pouring in. Unfortunately, most of them did not take this deep and meaningful question in the serious light I had in mind.

However, one person said something to this effect: 

"take a chunk of something and remove everything that doesn't look like a horse and you will have a horse".

That was enough to get me thinking about software development and maintenance in a new light. Perhaps a bit less deeply and meaningfully than originally intended. But one must work with what one has. Kind of like creating a sculpture.

Software maintenance a la sculpture would necessitate a top down approach. You have a body of code, thousands and thousands of lines of code (let's say we are working on the scale of Michelangelo's David as opposed to a Chinese tea cup). But in this case, years of helpful modifications have led to a few too many modules and unused and obscure Objects (reflecting my basic dislike of Java). Imagine David with an extra arm or long hair in a pony tail. Perhaps a pair of socks artfully turned down at the ankle. (I'm not going to photoshop this into reality but I invite you to do so and send it my way)

Removing the extra limb (unused modules) shouldn't be too hard - Delete Delete Delete. The primary tricky spot would be making sure that any dead end invocations were eliminated. We wouldn't want David to be left with an extra shoulder beckoning for that third arm to be added back on. The pony tail would be a bit trickier because we don't want to leave anyone with the aftereffects of a bad hair day, but the overall process would be the same.

Removing the socks (obscure Objects) is perhaps the biggest challenge. We don't want to render the feet unable to support the body, nor do we want to damage the elegance of David's stance. Hence, a careful examination of all the connections (direct, indirect) between Objects and identification of inheritance structures is just the beginning. Expert designers and coders with an eye for fine detail will need to be called in.

In the end: Voila! Beautiful, aesthetically pleasing code art of the highest quality. We may be on to something here.

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.


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.




Monday, May 2, 2011

Interdisciplinary Computing Meeting Number 2: Day 1, Part 2

In our afternoon discussion of faculty motivation for interdisciplinary computing (IC) I learned several interesting things. First the small but amusing: we had been flinging acronyms around quite a bit, and at one point someone used UTA right in the middle of a sentence. No one asked what this meant so I was brave. UTA: Undefined Three Letter Acronym. Cute.

Some food for thought items came out of the motivation conversation that addressed the questions (what is motivating about IC, how to support it) in a memorable way. I'll start with those.

 - "The transaction between 2 people in different domains is what makes each one better informed and knowledgeable." This might be taken as a a given, but it is interesting to consider it under the realm of "motivation". The affective side our reactions is often as or more motivating than the cognitive side of our reactions. If a synergy develops between two people discussing, brainstorming, and creating, then yes, this can be exciting (an affective response) - hence motivating.

- "It's data; it's representation. The domain doesn't matter". There were some interesting examples of this, such as all the ways to represent data in a form other than rows and columns or bar graphs. We saw a magnificent and beautiful simulation of what happens when people get into an elevator. Apparently this has been studied quite a bit. There are definable patterns of behavior that have a very mathematical predictability. The more data (people) you add, the more interesting the scenario gets. The collaboration was between CS and Art. We watched a colorful square show how people realign themselves as more people enter the elevator. For example, at first one or two or three (ish) people arrange themselves equidistant to one another. Then as more people enter, people spread out towards the walls, leaving a central open space. As more people enter, there is a shuffling around until everyone has almost exactly the same amount of space between them and are fully distributed through the elevator.

Now here is the even cooler part. If you REALLY want to make someone uncomfortable,  move over next to them - we watched this on the simulation as the little colored dots shifted around. If you do this, the other person will immediately try to reposition to regain their equidistant space. This can set off a domino effect of the entire elevator realigning itself.

Later on, a friend and I got in the elevator and watched people's behavior and yes, all of this was absolutely true. It all seemed to happen without anyone consciously thinking about it. We had a little conversation about whether or not we should test out the last part of the theory by engaging in conversation while casually moving closer and closer to someone. But we didn't carry through on that.

The elevator simulation was just one engaging example resulting from close collaboration and the synergy it produced.  It could not have been developed without the art and cs faculty in close communication.

Originality: One of the meeting participants gave us a short demo about teaching algebra using a rope. Someone suggested obtaining a video of the performance and posting it on YouTube. I sure hope that happens; I'll link to it. Hard to describe but the basic idea is that knot tying can demonstrate algebraic concepts e.g. "single instruction, multiple data = sheep shank". The premise is that math can be mapped onto many different systems; in this case the system was a rope. I'm telling you, the math concepts stuck in my head better than I ever remember from dragging my way through theoretical descriptions and chunking through example after example of plugging in numbers. We, the group, were transfixed and the presenter was clearly enjoying himself - very motivated.

We focused much of our conversation about Action Items (to support motivation for IC) in breakout groups. There are far far more than I can list here; some of them made it into my previous post. Many of the ideas related to putting in place support mechanisms to ease logistical hurdles (geographic, fiscal, advancement/promotion, departmental assessment/accreditation mechanisms, etc). The list was long. The ideas varied from top down to bottom up. Just to give you a flavor, here is one top-down item: Because they have clout, organizations, leaders, funders should voice public support for IC;  people who otherwise might not listen, will often listen if the message comes from someone in a position of respect and authority. One bottom-up item: hold a mashup of people who come together to discuss and address an issue: get them all in the same room to attack a given problem. (Sort of like what all of us were doing)
 
To try to sum up (a difficult task): An overarching action item: Develop a Framework of how to solve IC problems.

Sunday, December 19, 2010

Software and Art Authentication

I spent a few days up in the mountains unplugged. However, technology has an interesting way of creeping in even with the cellphone turned off (reception is unreliable anyway) and the laptop stowed. And I'm not going to talk about the visiting electrician who suggested that I test a 9V battery by licking it (he found this quite amusing, but I declined).

First, I was reading one of my alumni magazines and there was a story about a physicist who used software to examine highly controversial paintings that might or might not have been newly discovered Jackson Pollack works (full story here). The physicist, Richard Taylor, uses software to discover the presence of fractal patterns. Apparently, according to his research, true Pollack paintings are fractal filled. Benoit Mandelbrot agreed. Taylor also determined that fractal patterns reduce our stress levels. Interesting. (Has anyone investigated the effects of meditation while looking at fractals?)

There was a lot of money on the line in this particular situation, and apparently the politicking and public flame throwing were severe. As Taylor said in his article: "For the first time, computers were playing a significant role in determining the fate of artworks". The project was kept secret in order to protect its objectivity as well as Taylor himself. The full story reads a bit like a spy thriller. At one point he was advised not to go outdoors in case a bird dive bomb his head; at another point he was advised to he leave the country for a short while! Eventually his analysis, later supported by other evidence, determined the paintings were fakes. (This was about the time he was told to flee to New Zealand). The process of using software to analyse fractals in artwork is now legitimized and used by many researchers.

Reading this article caused me to think of a similar activity on a smaller scale and closer to home. My father (who passed away in 2009) was an archaeological chemist and spent hours on end sitting at his computer developing FORTRAN code to analyse art. Over the years, he was called upon to authenticate ancient ceramics, paintings from the Middle Ages, and was always glued to stamps (he'd appreciate the little joke). Although the culture of ceramics and artwork is interesting, it was his analysis of stamp forgeries that was most unique as far as I (in my admittedly biased position) could tell. He was always programming programming programming and peering at these little bits of lines and ink. I never got to see his code, and I suspect it is now lost, but I'd give a lot to know more about what he was doing. Over the years I would periodically be ordered off on a mission to obtain some obscure piece of software that he wanted to use, or to locate a specific piece of share-ware that he had somehow learned about. Fortunately he published more articles than I could ever read and a few books, so I can read his results even if I cannot see the code that produced it. If those subjects interest you too, here are a few books: on ceramics (here and here), stamps (here and here)