Week of Jul 6, 2003

« Week of Jun 29 < Individual Entries > Week of Jul 13 »

Ayole's Water and Technology As a Catalyst for Change

charity, society & sociology, systems

July 11, 2003, 10:50 PM

First off, a quick apology for the recent slowdown in posting frequency. I've taken on way too many projects this summer and thus haven't had as much time to update this journal as I'd like.

Today I partially taught a lesson in the TCinC class I'm co-teaching with Matt. Matt has put together the lesson plans for most of the sessions we're redoing for Joe's class, and today he had us show a video to the students called The Water of Ayole.

The Water of Ayole is a video used by the Peace Corps to communicate the important concept that technology must be introduced into organizations along with the skills and systems necessary to maintain and develop that technology. The video itself is about a program to introduce water pumps into many third-world african villages. The basic problem this program is trying to solve is that many villages are reliant on water sources that are unsanitary, disease-ridden, far from the village (and thus take a lot of time and effort to collect), etc. This lack of potable water is responsible for the deaths of thousands of Africans every hour. To solve this problem, the program funded the construction of water pumps that are capable of drawing water from deep underground that is pure, potable, and close to the village (and thus much easier to gather).

Unfortunately, although the intentions of these programs are good, the execution was flawed. Here's what generally happened:

  1. The government came in and funded the construction of the water pump. The villagers were overjoyed.
  2. A couple of years pass. The pump breaks.
  3. The villagers complain to the government, but the government doesn't have the money to maintain the pumps for free.
  4. The villagers attempt to raise money to fix the pumps, but they are poorly organized. The money is never collected and used appropriately.
  5. The women of the village go back to the time-consuming task of gathering the unsanitary water they drank before. Disease and death returns.

The exception to this rule is the village of Ayole. When the interventionists brought the pump to Ayole, they didn't simply build the pump and leave. Instead, they helped teach a mechanic who lived in the village how to repair the pump. The villagers themselves formed committees who were responsible for discovering problems with the pump and raising money for repairs. They even engaged in communal farming to help raise money for pump maintenance as a common good for the village.

Clearly, this video demonstrates the importance of organizational change when incorporating new technology. But I took another message away from it as well. I've always believed that true, lasting change can only occur if it happens in the hearts and minds of the people, and thus technology cannot, by itself, create change. However, technology can be a catalyst for change. The villagers in Ayole remarked that their community had grown stronger as a result of the pump, that the presence of the common good brought them together, even in ways that were not related to pump maintenance. They now took a greater interest in each others' affairs, and were more willing to help fellow villagers in need. Of course, this change did not come from the pump per se; it was the result of the organizational change that swept through the village as a response to the need to maintain the pump. But the pump undoubtedly spurred this change. Introducing a new technology can, when other conditions are right, tip the scales in favor of a new, better social order. And I think that's pretty exciting, especially for a budding technologist who hopes to do some good in this world.

Commentary

Posted by Tom Rudmik on April 01, 2004 at 03:46 PM

I am trying to get a copy of the Water of Ayole video. The UN is no longer producing the video. Since it is out of production you can make a copy of it without violating copyright. If someone can help us it would be greatly appreciated.

Thanks,

Tom

Posted by Daniel Scott Owen on July 27, 2005 at 09:23 AM

I am trying to track down a copy of this tape as well... Any hints?

Posted by sshan on March 16, 2007 at 12:29 AM

I want to buy the vedio for my class.
Would you please tell me where to buy?
Thanks very very much!

Got Something to Say About This?

Email Rob:

OR Post a Comment:

 

Enter the number below into the text box next to it.*


 

* These fields are required. Your email address will not be publicly displayed. Your web address is optional, and will be publicly displayed if provided.

Allowed HTML: a href, strong, em, ul, ol, li, blockquote, dl, dt, dd, dfn, code, q, samp, kbd, var, cite, abbr title, acronym title, sub, sup

Photographing Miss Bodine

aesthetics, people, personal

July 08, 2003, 12:42 AM

This entry is private. Forgot the password? Ask the Keymaster!

Commentary

Posted by Kenneth on July 13, 2003 at 08:37 PM

Nice pictures, Rob...however, for portraits in direct sunlight, you really want to use fill flash (that is, force the camera to use the flash, if possible at somewhat less power than normal). That way, people don't have shadows on their eye sockets and necks, which makes them look a little nicer. :-) That said, the outside one still turned out very nice; good job.

Posted by Rob on July 15, 2003 at 12:19 PM

Hi Kenneth,

Yeah, I'm familiar with the fill flash advice; I turned the flash off for those pictures since we were taking lots of indoor shots and it was ruining the natural lighting of the scenes. That said, sometimes firing the flash screws with the camera's light meter and might have caused it to underexpose the sky, but I should have tried shots with the flash on and off to see which came out better. Keep in mind this was around the 50th picture I took of Kerry that afternoon, so some of the variables had fallen out of my brain at this point, I fear. :)

Posted by Dan on July 20, 2003 at 11:56 PM

Where are the nudes?

Posted by Rob on July 21, 2003 at 03:37 PM

You have to subscribe for those... >;-)

Got Something to Say About This?

Email Rob:

But Is It Art?

aesthetics, philosophy

July 07, 2003, 09:29 PM

This week in Communication Design Fundamentals we got a new instructor, Charlee Brodsky, who is going to give us a crash course in photography (which I feel very lucky for getting; apparently last year CDF was almost entirely focused on typography and the students didn't work with images hardly at all). In class, Charlee brought in several photography books as an introduction to the medium; one of these, a book called Shopping, sparked some controversy as well as an interesting philosophical discussion on the definition of art.

Shopping is a series of photos taken from inside a number of department stores in a shopping mall, including several of partially or fully nude women in dressing rooms. The controversial bit is that the photographer took these pictures from a hidden camera in her purse. As far as we could discern, she did not get anyone's permission to take these pictures or to publish them. The faces of the subjects are not hidden in any fashion.

Charlee's position was that, although this was objectionable, it was less of an invasion of privacy than the "reality tv" shows that are so popular nowadays. Kerry took issue with this statement (being a fan of reality tv herself), and pressed Charlee's claim that Shopping was "high art" intended for an elite group of social critics whereas reality tv was "low entertainment" intended for popular consumption (my paraphrase, not her exact words).

This lead to an interesting digression into what makes art "art". Here's a few of the points my fellow classmates made:

All this reminded me of the course in philosophical aesthetics I took back at Virginia Tech. In that class, we examined questions such as "What makes an artwork an artwork?". The most plausable theory we examined in my not-so-humble opinion was George Dickie's institutional theory of art, or the "Art World" theory. Dickie argues that art is defined purely socially, and an object becomes an artwork when a member of the "Art World" calls it an artwork. I was never entirely clear on the qualifications for membership in this Art World, but as near as I could tell pretty much anyone interested in art could qualify as a member of the Art World. Thus, although my left shoe is just a shoe right now and not a work of art, if I were to call it a work of art and got it into the Museum of Modern Art with a nice little placard and everything, then suddenly it would become an artwork, and not just a shoe.

If you buy Dickie's theory, then in essence Charlee's original argument is correct, although she couched it in unnecessarily biased language: Shopping is art because a certain group of people who consider themselves to be in the business of creating and criticizing art have decided to call it art and treat it the same as all the other art they create and criticize. Reality TV is not art because no one has treated it in this manner. But this is the primary relevant difference; no intrinsic characteristics of either work directly matter in determining its artistic or non-artistic nature.

On a side note, after the discussion ended Charlee asked us to give a "thumbs up or thumbs down" for Shopping (intermediate angles of thumbage were also acceptable). I gave it an in-the-middle-thumb, up from the thumbs down I would have given it purely because it served to launch an interesting philosophical discussion. It's been awhile since I've come across any work of art I could say that about :).

Commentary

Posted by Dan on July 09, 2003 at 10:59 PM

This whole conversation reminded me of one I heard about when I was an undergrad. There was a lot of arguement about whether Rachmaninoff produced "art" because he mainly wrote music to entertain and was a "popular" artist. Popularity != Art in the minds of many.

High-minded folk forget that one of the purposes of Art is to Delight. I enjoy well-crafted TV the same way I enjoy well-crafted books, movies, music, and photographs.

Posted by Rob on July 10, 2003 at 04:38 PM

Sadly, I agree with pretty much everything you just said. I was hoping to stir up a bit of controversy with Dickie but it didn't look like it worked.

Generally speaking, I'm pretty pragmatic when it comes to art or entertainment or whatever you want to call it. I find a piece of artwork interesting if it does either (ideally both) of two things:

1. I find it viscerally appealing (its beautiful, visually interesting, tells a good story, etc). I think this is what you're getting at.
2. It makes me think about something differently than I did before (if only slightly). The various forms of art have powers as communication mediums that is different from the power of rational argument. I like it when a work leverages this power to force me to see some idea or situation in a new light.

Some people call (1) "low art" and (2) "high art". I tend to believe that's imposing an arbitrary value judgement.

To be fair, I'd like to append the comment that Charlee has distanced herself somewhat from this position in future class sessions. She's acknowledged that people see things differently and that there is a certain amount of subjectivity in art.

Posted by Dan on July 10, 2003 at 09:50 PM

It would be extremely hard to defend her original position. Are the Sherlock Holmes books art or just genre books? Is the music of The Beatles just pop? Weegie's photographs? Warhol's soup cans? The line is too blurry and too subjective.

Posted by Morgan Cqosh on November 30, 2004 at 09:20 PM

I find Dickies theories to be a bit contradicting. At one point he refers to art as an artifact that is manipulated through the hands of man, yet says that natural objects such as driftwood would be classified (remaing in its natural state) because attention is directed to it by an audience. His theories are too vague and open to the artworld, if I wanted to call used toilet paper art then its 'art'.

Got Something to Say About This?

Email Rob:

OR Post a Comment:

 

Enter the number below into the text box next to it.*


 

* These fields are required. Your email address will not be publicly displayed. Your web address is optional, and will be publicly displayed if provided.

Allowed HTML: a href, strong, em, ul, ol, li, blockquote, dl, dt, dd, dfn, code, q, samp, kbd, var, cite, abbr title, acronym title, sub, sup

The Agony of Getting Started

personal, software development

July 07, 2003, 12:23 AM

Whenever I start a largish programming project, I always fall into the same trap. As with any complex undertaking, I always find there are many, many things the project requires me to understand that I don't; there are many uncertainties or "risks" as the software engineering people like to call them. This freaks me out. I hate uncertainties; as a (mostly) INTJ, I prefer to work in areas where I know what's going on, where I feel that my knowledge and competence will carry me through with few difficulties. And so I wind up following an algorithm similar to the following:

  1. Procrastinate starting for as long as possible by basically pretending the problem doesn't exist. The more uncertainty, the harder I find it to get started, since that would mean facing the uncertainty.
  2. Try learning everything at once by madly flipping through books, searching the web, etc. to try to get some information that might help clear up the uncertainties. Give up when I realize there's no way I'll ever read and retain all the information I need.
  3. Think through the whole system to try to address every problem up front. I tend to go through a lot of dry erase marker and loose sheets of paper in this stage. Give up when I realize I'm never going to get it perfect on the first shot.
  4. Sit down and start writing some code, breaking up the problem into smaller bits and solving each bit one at a time. Learn what I need to when I need it. Fix mistakes as I come across them. Find that this really isn't such a tough problem after all.

This algorithm works, but I'm afraid it's not very efficient. Steps 1 through 3 could easily be cut out, saving me possibly days worth of time and immeasurable amounts of sanity. Yet no matter how hard I resolve to follow this wiser course "next time", I always realize after several days of agonizing that I just slogged through steps 1 through 3 once more. I'm wondering how many times I'm going to put my hand in the fire before I learn that orange-flashy-stuff-no-touch.

In short: yes, Newsable is coming along just fine.

If you ever find yourself in a similar situation, just remember that no amount of forethought can replace the experience of actually writing and testing code! This isn't to say that a bit of up-front design isn't helpful, as long as it's done in moderation. Just don't get carried away and forget that you aren't really getting anything done until you're down in the trenches mixing it up with the compiler and its nefarious code libraries.

On a completely unrelated note, according to Movable Type this is my 100th post to roBlog. I kinda feel guilty that it didn't turn out more insightful than this...

Got Something to Say About This?

Email Rob:

OR Post a Comment:

 

Enter the number below into the text box next to it.*


 

* These fields are required. Your email address will not be publicly displayed. Your web address is optional, and will be publicly displayed if provided.

Allowed HTML: a href, strong, em, ul, ol, li, blockquote, dl, dt, dd, dfn, code, q, samp, kbd, var, cite, abbr title, acronym title, sub, sup