Tag Archives: storytelling

Beginner’s Eyes: on storytelling and growth

John D. Cook, in a short, poetic post, describes how experts end up where they started, as beginners, and why, in his blog post “Coming full circle”. A few folks in his comments thread make the connection with Zen’s concept of “Shoshin”, the Beginner’s Mind, and it does, but I hear echoes of another journey just as strongly.

YouTube: “The Hero’s Journey / Monomyth”

Visualizing the news: on storytelling

Matthew Ericson of the New York Times (and former co-worker of mine) put together slides of his recent presentation at AIGA Pivot. The presentation must have rocked because the slide deck, while short on details, is rich in thought provoking: PDF.

For a recent example from his team, check out today’s interactive on the Euro debt crisis.

On Making and Working Towards Big Things: on innovation

Wondering why we’re living in an age of ever increasing decreased expectations? You are not alone. Author Neal Stephenson wrote a thought provoking must read for World Policy Institute titled, “Innovation Starvation”:

The imperative to develop new technologies and implement them on a heroic scale no longer seems like the childish preoccupation of a few nerds with slide rules. It’s the only way for the human race to escape from its current predicaments. Too bad we’ve forgotten how to do it.

The Twelve Doctors of Christmas

Tor.com ran a great series of essays on each of the Doctors titled “The Twelve Doctors of Christmas” that has some good reads.

My favorite essays out of the bunch:

“The Third Doctor”

“Born to be an Alien”

“Shifting into Fifth”

The Walking Wounded”

3, 4, 5, and 9. Pretty much coincide with my favorite Doctors as well. No offense all of you out there.

“Born to be an Alien” quotes an essay that was passed along a while back that is still a good read, “How Doctor Who Made Me A Liberal”. Sometimes I feel like I should write a version of this essay wrapping in Star Blazers, Star Trek, early Star Wars, and the Muppets because they, along with Doctor Who, left some similar imprints on me growing up.

The stories we are told as kids stay with us in some interesting, and powerful, ways.

As the series summarizes:

Until next time, remember: Bananas are good, Daleks are bad, try reversing the polarity, and intellect and romance should always triumph over brute force and cycnicism.

NPR covers Mark Horvath’s Invisiblepeople.tv

I try and spend some time each week serving lunch at Project H.O.M.E.’s “Women of Change” with other fellow CIM Volunteers. I’m engaging some of the folks who work at Women of Change into possibly trying a project along these lines. I think Mark Horvath is onto something by sharing these stories as raw as he does.

NPR.org: “Former Homeless Man’s Videos Profile Life On Street”

Reference Links:

Invisible people.tv

Mark Horvath: haRdLy NOrMal

Jeneane Sessum rocks – Why Journalism Matters

We become part of the stories we discuss on our blogs. We mold, change, and affect the public’s perception of the people, places and events we talk about, via Google’s lasting, aggregating lens.

More and more evidence points to Jeneane Sessum being unfairly connected to the matters I posted about yesterday and her good name has been drug through the mud. That mud leaving trails all over Google.

As Jeneane says:

There are layers and layers of important issues that intelligent people can tackle and use to make meaning out of this. I hope that effort moves forward.

Me too.

So while folks are discussing the code of conduct suggestions over at Tim O’Reilly’s, I’d like to remind folks of The Citizen News Network and Center for Citizen Media project – Principles of Citizen Journalism, and think about that first principal – Accuracy – before passing on information that isn’t proven again.

As Scott Karp says, this entire episode illustrates “Why Journalism Matters”:

I have been watching in silent horror for days as this drama has unfolded – horror not only at Kathy Sierra’s traumatization, but over the total unrestrained free-for-all in the blogosphere. This is a case study in hearsay, innuendo, rumor, defamation, libel, jumping to conclusions and every other negative consequence of unrestrained publishing that the principles of journalism are intended to prevent, and notwithstanding some notable failures, generally do prevent when applied with some seriousness of purpose.

I read dozens of blog posts on this incident, and I still had NO CLUE who might or might not be guilty of what. Each new post I read tangled the web further, layering misinformation on top of disinformation. There was precious little “WHAT do I know” and a whole lot of “WHO do I know and how do I feel about them.”

Then I read this article by a JOURNALIST at the San Francisco Chronicle. I can’t say for sure whether all of the fact here are straight, but this is the only place I came across that actually attempted to ascertain through a coherent process what the facts might be or to lay out a coherent sequence of events. AND, you’ll notice that the only names of those (alleged) to be directly involved in the incident that the article mentions are Chris Locke and Kathy Sierra, both of whom the journalist interviewed and quoted. In the blogosphere, naming names was all about shoot first and ask questions latter.

Update: Anyone can commit acts of journalism. With this story, the fact is, few of us actually did. And the consequences are no good for anyone.

Update: There should be a “Clay Shirky rule” for social software discussion threads…

First person to make a connection to a Clay Shirky piece gets props or insults or something like that….

I bring this up because so much of this series of events recalls an old Clay Shirky piece worth revisiting: “A Group Is Its Own Worst Enemy”:

…We’ve had social software for 40 years at most, dated from the Plato BBS system, and we’ve only had 10 years or so of widespread availability, so we’re just finding out what works. We’re still learning how to make these kinds of things.

Now, software that supports group interaction is a fundamentally unsatisfying definition in many ways, because it doesn’t point to a specific class of technology. If you look at email, it obviously supports social patterns, but it can also support a broadcast pattern. If I’m a spammer, I’m going to mail things out to a million people, but they’re not going to be talking to one another, and I’m not going to be talking to them — spam is email, but it isn’t social. If I’m mailing you, and you’re mailing me back, we’re having point-to-point and two-way conversation, but not one that creates group dynamics.

So email doesn’t necessarily support social patterns, group patterns, although it can. Ditto a weblog. If I’m Glenn Reynolds, and I’m publishing something with Comments Off and reaching a million users a month, that’s really broadcast. It’s interesting that I can do it as a single individual, but the pattern is closer to MSNBC than it is to a conversation. If it’s a cluster of half a dozen LiveJournal users, on the other hand, talking about their lives with one another, that’s social. So, again, weblogs are not necessarily social, although they can support social patterns.

Nevertheless, I think that definition is the right one, because it recognizes the fundamentally social nature of the problem. Groups are a run-time effect. You cannot specify in advance what the group will do, and so you can’t substantiate in software everything you expect to have happen.

Now, there’s a large body of literature saying “We built this software, a group came and used it, and they began to exhibit behaviors that surprised us enormously, so we’ve gone and documented these behaviors.” Over and over and over again this pattern comes up. (I hear Stewart [Brand, of the WELL] laughing.) The WELL is one of those places where this pattern came up over and over again.

Well worth reading if you never have, or re-reading if you did a long time ago.

Adrian Holovaty: “Newspapers need to stop the story-centric worldview”

Adrian Holovaty: A fundamental way newspaper sites need to change:

This is a subtle problem, and therein lies the rub. In my experience, when I’ve tried to explain the error of storing everything as a news article, journalists don’t immediately understand why it is bad. To them, a publishing system is just a means to an end: getting information out to the public. They want it to be as fast and streamlined as possible to take information batch X and put it on Web site Y. The goal isn’t to have clean data — it’s to publish data quickly, with bonus points for a nice user interface.

But the goal for me, a data person focused more on the long term, is to store information in the most valuable format possible. The problem is particularly frustrating to explain because it’s not necessarily obvious; if you store everything on your Web site as a news article, the Web site is not necessarily hard to use. Rather, it’s a problem of lost opportunity. If all of your information is stored in the same “news article” bucket, you can’t easily pull out just the crimes and plot them on a map of the city. You can’t easily grab the events to create an event calendar. You end up settling on the least common denominator: a Web site that knows how to display one type of content, a big blob of text. That Web site cannot do the cool things that readers are beginning to expect.

I left a comment responding to a poster saying this sounded like the Semantic Web, I’ve been meaning to write Adrian for a while now as well:

Hello Adrian,

I’ve been meaning to say hello to you for a number of different reasons over the past few years.

I’m an old Knight Ridder Digital developer. One of the folks that helped develop the Cofax CMS that was later replaced by KRD with… something else.

Cofax was a framework as well as a CMS, and in some very positive ways (well *I* think so :)), Django reminds me of it. Cofax was open sourced, but when KRD replaced it, well, work pretty much kept me from going back, refactoring, and taking it where it could still go. It’s still in use in many places. Well enough of that…

I definitively agree with you that newspapers are terrific places to work if you are a software engineer. The pace is quick, the work challenging, and you get the rare opportunity to not only practice your profession, but do so building tools and services that connect, inform and empower people.

It’s hard to beat.

anonymous – yes, I think Adrian is talking Semantic Web here. But like Adrian’s call for newspaper organizations to take a hard look at how they manage information in their publishing systems, Tim Berners-Lee has made the same call to the web developer community. The hard sell has been that that the Semantic Web likewise solves a series of problems of lost opportunity. It requires an investment in time and effort by the developer community to see its potential archived. Adrian, please correct me if that’s an incorrect understanding on my part.

Great piece.

Related reading material: Aaron Swartz: “The Semantic Web In Breadth” and Shelley Powers: “The Bottoms Up RDF Tutorial”. Then there’s “Practical RDF” also by Shelley Powers (which I ummm need to get around to reading, but have always heard good things about).

More at Techdirt.