What is an API?

I have been doing little editing/clean-up bits for the upcoming “Stewarding Technology for Communities” book and one of the things we want to get right are the technical terms – and we want them to be understandable to people who may not be techies. One that I was chasing down yesterday was API, or Application Programming Interface. I wasn’t clear if APIs opened up access to functionality, the actual code, or both. I decided to ask my Twitter friends. Here is what I learned – I thought I would share it with you.

reply to NancyWhite

  • davecormier @nancywhite it’s like exposing the underside of a lego block. if you make your block to fit the holes, you can connect to it 04:27 PM January 02, 2008
  • D’Arcy Norman dnorman @nancywhite: APIs expose functionality so you can write your own code to incorporate it. 01:17 PM January 02, 2008
  • Chris Lott fncll @NancyWhite also depends on what is meant by “access” to code– a proprietary system w/API can provide access to code 11:13 AM January 02, 2008
  • Chris Lott fncll @nancywhite APIs provide access to existing functions, code and data, any or all of which can be used to further functionality. 11:12 AM January 02, 2008
  • Scott Leslie sleslie @nancyWhite forget what I just said. I thought you were asking a different question. Just waking up. 11:42 AM January 02, 2008
  • Scott Leslie sleslie @NancyWhite both, it depends. Some API’s focused around giving you functionality, other’s around data (though w/ data, there are other ways) 11:41 AM January 02, 2008
  • Jan Karlsbjerg JanKarlsbjerg @NancyWhite API’s make FUNCTIONALITY accessible to other programs/programmers. 11:38 AM January 02, 2008
  • Lion Kimbro LionKimbro @NancyWhite: APIs make functionality accessible. Even if code is available, I wouldn’t necessarily call it “accessible.” 12:21 PM January 02, 2008

I’m not a whale

phytoplanktonI pretty much ignored work, blogs, and Twitter over the holidays to be more present with my family and to give my brain a break from thinking about work all the time. (By-product of a work-a-holic practice.) I did go through my Twitter contacts and accept all the requests to follow. Then I made my feed public. It was the “Return of the Plankton.” The convergence of those two things put me over the edge. The flow from Twitter was more than I could digest. I lost the feeling of intimacy of connecting with friends and friendly strangers.

Then I read Jim Benson’s recent post on Twitter, Seeds of a Meme. And I started nodding.

Twitter has been called a conversation ecosystem. It is actually part of a larger conversation ecosystem that includes .. well .. everything. Blogging, Facebook, email, chats at a coffee shop, daydreams.I see Twitter as a plankton layer-level of the ecosystem. Every animal on earth does not need to eat plankton, but without plankton we’d all be in a world of hurt. “Everyone twittering” seems like an absolute nightmare.

Everyone will not be twittering.  Everyone will not be blogging.

But conversations will start in one medium and move to another and then another.  From Twitter to blogs to mainstream media to public discourse.  Twitter and its successors will seed the conversations of the future.

White filter feeding anemone

Spot on, Jim.

From a practice perspective, I have to trim back down the number of people who follow me. I’m not sure I care if my feed is public or not, but it does act as a filter on requests to follow and discovery of new people. It’s not that I’m against discovery, I just can’t handle the volume.

I am not a whale, a filter feeding white anemone, damselfish, nor a basking shark. I do not eat plankton as my primary diet. My form does not have enough of those feathery things, with large surface areas to filter in all the phytoplankton. For my phytoplankton (Twitter) is seasoning to the rest.

Hoosgot: Reciprocity and Community Indicator Rolled into One

Dave Sifry is filling the quiet end-of-year time with a project that makes it easy to ask and answer with and for each other online in a variety of ways. Sifry’s Alerts: Announcing Hoosgot: Resurrecting the Lazyweb

Today I’m unveiling a new service that I put together over the last 48 hours. It’s called hoosgot.com. Hoosgot (pronounced “who’s got…”) is a simple way to ask who’s got what you’re looking for. Just put “hoosgot” in a blog post or a Twitter tweet and it’ll show up on Hoosgot. Send a twitter to @hoosgot, it works as well. You can tag a post with hoosgot or lazyweb, and we’ll pick it up as well, as long as your blog is indexed by Technorati. It’s meant to give you a place to send the requests for all of those things that you’ve wanted, but just can’t find – chances are, what you want already exists and someone else out there in the ether knows about it (or has built it!)If someone’s got what you’re looking for, or a clue in that direction, they post a comment. RSS feeds flow from the posts and the comments.

For example, you might ask:

hoosgot an easy-to-use pencil sharpener that has suction cups on the bottom so I can stick it anywhere?

or:

hoosgot a simple camera bag that you can stick a laptop in, and still carry over your shoulder without knocking over pedestrians? Note I’m not looking for a knapsack or a backpack, I want it to act like a messenger bag…

And so on.

It works if you work it: Give back to the web

Of course, you should subscribe to hoosgot, it has RSS feeds (the main feed and the comments feed) so you can watch and participate – for Hoosgot only works if you comment on the questions posed. Happen to know where someone can find the information they seek? Interested in collaborating with them on creating that invention described when the person invoked hoosgot or the lazyweb? Leave a comment on the entry, and give back to the web that has given us so much.

Hoosgot is a great community indicator in that it has its roots in the work of an earlier community (Lazyweb) and many individuals, it is offered as a gift to the world, and it lives that value in the very service it offers. Pretty sweet. Thanks, Dave.

Learning Over Each Other’s Shoulders

(Note: this  blog post dates from September 13th 2007 on my old blog. It had  been in limbo since August 30th. There was so much more to add, but I decided it is time to put it in the wild and not lock the partial thinking in the “draft” queue! Now I am republishing it today as I have a coda to add and the older blog post is hard to find…)

The Original Post

I have been part of quite a few informal conversations recently about how to “learn how to do this web 2.0 stuff.” Not just learn it, but learn it in the context of it adding something useful to our work and lives. The volume, the subtleties of useful practice, can feel overwhelming. Our sense of inadequacy can paralyze.

In Cali, Colombia, I led a workshop about facilitating online interaction and we used the Social Media Game to add context to this flood of “cool new tools with weird names. ” I think the most engaged moment was when people were in small groups, explaining new tools to each other and thinking about what might be useful in their work. It was still pretty abstract. We did not get hands-on. But people noted that the tool stuff was of a great deal of interest.

I always try and promote the people and process stuff, but the reality is that tools are often the “door opener” to the process conversations because they are more tangible. So being able to “look over the shoulder” as someone uses the tools in a social context would be really useful.

In Bogota, Colombia at the very well attended “Quality in eElearning” conference I had a side conversation about ways to usefully use Twitter, Wikispaces and del.icio.us with a couple of my co-presenters, and a separate conversation with Jay Cross about doing an “Over the Shoulder” camp. Inthe instance with Ulf-Daniel Ehlers it didn’t start out as a conversation. I had mentioned and showed a Wikispaces page in my presentation the day before. During the third day where we were relaxed in the “participant” role, I was sitting next to Ulf and noticed he was messing with a wikispaces page he had set up. I showed him a couple of things. He shared a few links. Together, we figured out how to embed del.icio.us links into a Wikispaces page from a great blog post I had found a while back. In the mean time, Virginie Aimard was looking over from the other side, following silently along on our digital journey. Back and forth.

A few weeks later I was the guest for a “10 Minute Lecture” for Leigh Blackall’s Online Learning Communities course, centered in New Zealand. (You can see the slides, audio and Elluminate recording here.) The theme was peer learning – a communities of practice perspective. Leigh had initially asked me to talk specifically about Peer Assists, but I felt a larger issue tugging at me – this “over the shoulder” stuff.

We talked about this mode of learning from each other. I really enjoyed the conversation and poof, the hour was up. But then the blog posts from course members started showing up – those who were in the live session and those who viewed the recording. There the themes of inadequacy, of the pressure of time to do this learning, of possibility. I felt this little frisson of learning, that was a bit of learning over each others’ shoulders. For me, it was then important to comment on each of the blog posts that mentioned my name, thus showing up in my feed reader, because learning from each other has that back-and-forth quality. It is iterative. Conversational.


And so this thinking, doing, experiencing, advocating for over the shoulder learning comes back to a reflective blog post. Because reflection is the final piece that cements it together.
Comments from the original post on Blogger:

2 Comments:

Anonymous Beth Kanter said…
Nancy: I love the idea of “over the shoulder” camps. At one point, durin my circuit riders – we used the term “shoulder-to-shoulder” to describe informal, small group computer instruction. So, what you are talking about is the network effect of this type of learning?

3:20 PM
Blogger annelizbeth said…
Fascinating…absolutely fascinating. I am currently engaging in an effort to provide a perspective on the state of “learning” for a npo client…will be sure to include your futuristic thoughts around where we are headed…!

7:43 PM

Today’s Update

I have been sick with the flu the last 10 days, eliminating any chance of finishing my year end work and having time for reflection. I have an RFP that I have to respond to this week so I was reviewing some of my pertinent materials – particularly those related to peer learning and online facilitation.

I realized I have never classified much of my work as “peer learning.” More often this has come under the rubric of learning from and with each other in networks and communities (i.e. communities of practice, etc.) I have had a bias for on-the-job, in-the-moment, just-in-time and informal learning, supported with appropriate formal and structured learning. These peer based options give us the opportunity to learn both in context and with the give and take that reveals the texture and nuances of those contexts.

It is beyond obvious to state that digital technologies have expanded our possibilities for these peer learning forms. So the reflective question going back, and the learning agenda question going forward is what will advance and deepen our ability to learn with and from each other in the coming year?

What do you think?

Circles of love, chocolate, gifts and downtime

Today I was sent a link to Connecting Dotz … Linking people with ideas with people with ideas… and their lovely cards of the Osani: Circle of Love Game. Osani Circle. This struck just the right holiday note for me. Sitting in a circle. Feet touching, playing a the Love Game.

As I enjoy some time off with my family in the drippy, cool Northwest of the US, know that you are all in my heart, in corners big and little, in acquaintance deep and light. I wish you a new years full of learning, love and good health. I wish our world peace, wisdom and joy.

I have made donations to the following organizations in your collective names:

And for your stomachs, here is my family’s tradition – Fudge!

Put in large bowl:
(really big, big, big to allow stirring room):

  • 3 packages chocolate chips – 36 oz. total (I recommend Nestles or Guittard — don’t go cheap!)
  • 1 8-oz jar marshmallow cream (if you can only find 7 oz jars, that’s OK)
  • 2 cubes butter (buy a brand name — sometimes the cheap stuff is full of water and it will ruin the fudge — very sad)
  • 1 teaspoon vanilla extract

Have ready at hand:

  • 2 cups chopped nuts (optional — you can even add coconut!)

Put in large kettle:
(again, I mean big – the mixture boils up to four times it’s original volume as you cook it!)

  • 4 1/2 cups sugar
  • 1 can evaporated milk (not skim or lowfat!)

Bring the sugar/milk mix to a rolling boil stirring constantly. Cook a full eight minutes (timed once the mixture comes to a boil — critical!!!).

Take off heat and pour over chocolate/butter mixture. Beat with mixer until creamy. Add nuts and spread in a pan to cool. Lick the bowl and beaters before washing! I like to use a cookie sheet with high edges, but the size of pan depends on how thick you like your fudge. Mine is about 13×24. My siblings use smaller pans. My mom uses two Pyrex pans. Cut into pieces and enjoy!

Now it is time for some “downtime.” Forgive me if I ignore your emails, twits and posts for a few days. Time for  meals, conversation, books, puzzles, games and just some plain ole NUTHIN!

Happy Holidays

Nancy