Category: development

  • Enabling Creativity

    Max and I presented today at the Telfair’s Pulse art and technology fair for “family day”. Our presentation went over some of the fun stuff we’ve done together with technology and how people can get their kids to find creative outlets through geekery. We had a lot of fun, and Max had a blast presenting (he did a great job).\
    Here’s how we came up with the presentation:

    * Two weeks before the presentation, Max and I sat down and talked about what stuff we’ve played with he’d want to tell people about and built an outline.

    * I went back later and created the actual presentation, filling in the gaps and figuring out what I wanted to say in the intro and conclusion.

    * The week before the presentation, we practiced the demos and came up with the idea of having him tell me how to do everything (instead of the traditional “Mr. Wizard” style approach).

    * The morning of, we went through it again and made sure he had some idea of what he wanted to say during his parts.\
    I didn’t want to put a huge burden on him, since this was his first time in front of what could have been a large crowd. But, he was very involved in writing the presentation and walked me through all the demos.\
    He had so much fun that he wants to present again, maybe at this year’s Geekend.\
    Here are the slides if you’re interested:

  • Weird Dreams

    I had a weird dream last night (two, actually, but I’m only concerned about writing down the first one). In the dream, I was back at AOL sitting through a horrible product requirements meeting when I lost it and started yelling about how bad the requirements were, how they didn’t do anything original, were a waste of paper and no one would use this thing even if we built it (I don’t even remember what it was now). I got in a fight with the product manager, and all I remember of the screaming match was that she said something like, “You’re not the only ship on this sea, pal,” to which I replied… and I remember me screaming it: “Not the only ship?! I’m the sea!“\
    Then, I got fired. It was a strange experience, watching dream me pack up his crap in boxes and get escorted out. I lost it a few times in my thirteen years at AOL (wait, sorry, now it’s “Aol.”), and one or two of them almost got me fired, but those were early on when I was still in tech support. I lost it in meetings a handful of times (which I think is a pretty good record considering how many awful product meetings I sat through) and called BS where I needed to, but I don’t think any of them ever got me close to the “terminating offense” line.\
    Yeah, I don’t know what it means either, but I thought it was a pretty good comeback, especially for a dream.\
    The other one was a nightmare where I was Doctor Who. It was so scary, I actually woke up and had a hard time getting back to sleep. This robotic zombie fell on me, had me pinned to the floor and kept saying “I know what you are” over and over again. shudder.

  • An Introduction to Whuffie

    This is my third blog post for The South. You can check it out over there, or just read it here.

    In Cory Doctorow’s Down and Out in the Magic Kingdom, all the world’s shortages have been solved. There’s no need for money, because there’s no lack of supply. Even death has been conquered. In a world with no need for money, what’s the currency? Doctorow’s solution to this problem is called whuffie, a currency based on reputation. Everyone has a bank of whuffie, and anyone can give you a little boost or ding you based on your actions. My favorite part of the concept is that there are two types of whuffie – left-handed and right-handed. When you meet someone in that world, you get a little graph that shows you the whuffie that person got from communities or people you basically agree with (right-handed) and the whuffie that person got from communities or people you don’t (left-handed). In Doctorow’s book, the people with the most whuffie are those that do the most menial jobs: the janitors, plumbers, garbage men, etc.

    I read the book on a flight from San Jose to DC, and for five and a half hours, I was hooked. I finished the book about halfway through the flight and spent the rest of the time frantically scribbling in a notebook, trying to design a way to implement this concept in the real world, or at least on the internet. I was so fascinated that I spent the next several months trying to convince my company that we could actually implement it, and I still think it’s possible, and have implemented a crude whuffie system on Ficly.

    Why is the idea of currency based on reputation so interesting? Because when I look at the internet, I see that reputation is already the primary currency. In every community, there’s some concept of reputation, although usually unspoken. Every community has cultural norms, and rewards those that exemplify those norms and punishes those that don’t. The primary driver for almost every community on the web is not money, but something else. That something else is the source of whuffie in those communities. The other important point is that whuffie doesn’t travel. Just because you have a good reputation on one site doesn’t mean that reputation will travel when you join another. I believe it should at least provide some informative value to the communities I join. Don’t make me go through the usual new user initiation if I’ve got a good reputation on other sites.

    Let’s look at Flickr. The primary whuffie driver on Flickr is the photos people upload. Once you get a reputation as a great photographer, and have your photos show up on the Explore page, you’re considered a “success” on Flickr. But, there are many other valuable activities on Flickr, and on any social network, that should drive reputation but don’t. If you post the most constructive comments, there’s no quantified reputation for that… yet. If you post the most expressive and findable tags, there’s not quantified reputation or recognition of that very valuable contribution… yet. Both of those actions are extremely valuable to the community and are complimentary to the primary social object – the photo.

    Social sites like Flickr are perfect playgrounds to implement whuffie. They’re self-contained and have a limited set of reputation-building or damaging actions. On Flickr, those include uploading photos, adding favorites, tagging, posting comments, deleting things and participating in groups. Once you identify those activities, it’s then trivial to add values to those actions and increment or decrement a user’s whuffie based on their actions. This takes some of the gamesmanship out of other rating systems and can provide a way to reward the community-building secondary actions – like commenting or tagging – without detracting from the primary whuffie builder. That way, everyone is rewarded for their actions, and there’s an easier path to finding “bad actors” in the system. They could also make those first social interactions on the site easier. You could give people some clue as to the person’s reputation on your first introduction to them. How much easier would it be if you got some idea of how reputable someone was when you got that connection request on LinkedIn?

    There are people already working on implementing whuffie in the real world, and a lot more to it than what I’ve had the time to write. If I’ve piqued your interest, you should check out the Wikipedia page on whuffie. Tara Hunt has also written a great book called The Whuffie Factor about building and using whuffie in the real world, and someone’s even started a whuffie bank. I heartily recommend reading Down and Out in the Magic Kingdom (you can download it for free), though, as it still has the best examples and explanation of whuffie. If you’d like to talk about whuffie in person, I’m speaking about it at Geekend in a couple weeks!

  • A tip about the Pledge Drive

    See Kevin’s post to the left?\
    The way the pledge drive works is that if the goal isn’t meant, none of the money pledged will go to Ficly and no one will be charged. At this point to be so close to the goal is great, but Ficly continues to need that extra little bit to reach the ultimate the goal.\
    I just wanted to clarify things, since I don’t think the process is intuitive.\
    Thanks to everyone who has pledged!

  • SxSW and the Pledge Drive

    A couple links for you to click if you’re into that kind of thing:

    • My SxSW Panel submission – Called From Doer to Manager, I hope to talk about making the transition from individual contributor to manager and the steps in between. I don’t know who’s going to be on the panel yet, but the first step is to get votes! So, if you think it would make a good SxSW panel, I’d appreciate a click.
    • The Ficly Server Support Project – We’re 13 days from the deadline and still \$76 dollars short. You can pledge as little as a dollar and it all goes towards paying Ficly’s hosting bills for the next year.\
      There you go…
  • The Ficly Server Support Project

    Ficly is doing fine, and it’s a nice break from work stuff to go play in something uncomplicated without a bunch of dependencies. The community is great and they produce some fantastic stories.\
    As I mentioned in my previous post, I’m enamored with Kickstarter and asked them if I could create a project for Ficly to see if we could get the community to help us out with the hosting costs for the coming year. I figured \$800 would cover the co-location facility and our Amazon bill (we store all the images people upload there and probably some other stuff in the future), and maybe some upgrades to Ficly’s box (I just realized I should add more RAM, for example).\
    They said yes, and Wednesday night, I created the Ficly Server Support Project. In the first 48 hours, we’ve raised almost 75% of the total, and we still have 31 days to go!!\
    If you can help out, I’d appreciate it. Ficly’s not going anywhere, but the help is definitely appreciated and makes things a little easier on Jason and me.\
    Thanks!

  • The Future of Product Development

    I’ve been hearing about Kickstarter on various blogs this week. Well, I checked it out tonight, and I think it’s brilliant. It’s basically a way to run a pledge-based funding round for a specific purpose. A lot of the projects on the site are from artists who want to release an album, or filmmakers who want to make a movie. You have a certain amount of time to reach your funding goal. If you get enough pledges in the set amount of time, everyone’s credit cards are hit and you get your money. If not, no one’s out a dime. It could get bootstrapped startups off the ground, lead to truly independent art, and be a great way to crowdsource journalism. But, I think it could be the future of product development. If your users really want a feature, do they want it enough to pay for it?\
    Here’s how it could work:

    1. User requests a feature through Get Satisfaction
    2. Product Owner decides whether they want to build this feature and sets up a pledge for it on Kickstarter – setting a price based on complexity + time to implement * desire to build it (0 being “I was going to do it anyway and it will take five minutes, so why bother, 1,000 being I really don’t want to build it, but if you give me \$100,000, I’ll consider it).
    3. Product Owner posts the link to the pledge and the amount required to build that feature.
    4. If the pledge succeeds, the feature gets implemented. If not, it doesn’t (unless the Product Owner really wants it).\
      For large companies, this doesn’t make a whole lot of sense. But, for small companies who have few resources and little time? This could make choosing what you work on next a really easy decision, and involve your users in the process.\
      If anyone actually does this, I’d love to hear about it.\
      And to prove I think it’s a great idea, I’ve pledged to support a zombie movie being shot right here in Savannah. Check it out… let’s help this guy make a movie!!\
  • Rails in Athens

    I was in Athens, GA yesterday speaking to the DWEEBS group at the University of Georgia about Rails. It was a lot of fun. Afterwards, I went out to lunch with Jinny Potter (the head DWEEB) and Kara, our former intern who’s now attending UGA, and then Jinny took me on a tour of the university and downtown Athens. It was a great time, and Jinny was a great host.\
    Here are my slides from yesterday if you’re interested. I’ll be giving some form of this presentation at August’s Refresh Savannah.

  • Ficly.com is the place to be

    Wow, I am really amazed at the reception the new site has received. Way to go, men!

  • Ficly

    It’s not done, but I nagged Jason enough so we’ve launched it anyway!! I present to you, my dear readers… Ficly. There’s a long story to tell about how any why Ficly came to be and why we couldn’t leave well enough alone. I might as well tell it.\
    Building ficlets, for both Jason and me, was the best experience of our professional lives (he told me that, anyway, and I believe him). We had total freedom to do the right thing, which is rare, especially at AOL. We, along with Ari, Cindy and Jenna, built something beautiful. And then, it all sort of went weird. Everyone eventually left AOL, and I was left alone to keep the site kind of up and running even though I’d been told I wasn’t allowed to work on it anymore. Then, I left AOL last summer to go work at Music Intelligence Solutions on stuff I’d never done before.\
    In December, AOL announced that ficlets would be shut down. I went and created the ficlets memorial, because it would be criminal to let all those stories just disappear. A bunch of valiant souls still inside AOL battled hard to get the company to either give me ficlets outright or donate it to a non-profit – it obviously didn’t happen. Jason and I e-mailed back and forth a few times about how sad it was to see ficlets die and that we really should do something about it. But, who’s got the time?\
    It was Jason who pushed until I agreed. Jason got Tom Osborne and Owen Shifflett from Viget Labs to jump in and save the day (because you really don’t want me designing anything). They designed what you see on the site, and it’s more than I could have hoped. Our pal Joe helped out when he could, and I worked a couple hours at night during the week and a few hours on weekends when I wasn’t working late at the office. Five months later, and several helping hands later, here we are.\
    I’m extremely happy with how it’s turned out, and with the reaction from the community so far. We wouldn’t have built Ficly if the ficlets community wasn’t so great. We did it for them, and because we have a lot of fun working together – even when it’s over e-mail.\
    I don’t think of Ficly as a “side” project and we’re certainly not a startup. Ficly is an art project. We built it out of love – and a passion for fostering creativity. I think Jason put it best in an e-mail, “My job isn’t building web pages. It’s delivering happiness by the kilobyte.”\
    I don’t know where Ficly goes from here. I know I have a laundry list of stuff I wanted to do on ficlets that we’ll probably get around to eventually. For now, it feels good to have done what we’ve done so far. It was hard making time for it, but I’m glad we did.