Combinatorial Innovation

There are so many new technologies today: tablets, geolocation, video chat, great app frameworks. It is easy to cherry-pick off “combinatorial” innovations that seem compelling, and can maybe even be monetized readily.

But all those innovations are inevitable. If our technologies afford a certain possibility, they will occur. “That’s not a company, that’s a feature,” is one criticism I’ve heard of many “startups.”

These combinatorial, feature-oriented “X for Y” endeavors are often attractive because they can often be built quickly.

Startup Weekend events send an implicit message that a meaningful business can be fleshed out in just a couple of days. And I argue that is not true. That might be a good forum to get practice with building a quick combinatorial technology and working with others, but a real innovation, much less a meaningful business, takes real time.

I think people are often looking in the wrong places for innovation, often because they don’t really take the time to do the homework, observation, and deep reflection necessary to arrive at a true insight. We want things to be quick and easy.

Changing Minds, and Behaviors

The biggest innovations require asking people to change their beliefs, habits, and behaviors.

iPhone: “why would I want a smartphone without a physical keyboard? It’s too expensive. I can’t install apps.”

Twitter: “what is this for? Why would anyone do this? Who cares what I had for breakfast?”

iPad: “an expensive toy. Could never replace a real laptop. Can’t run real office applications. The enterprise will never adopt it.”

Foursquare: “only hipsters and bar hoppers would ever do this. They are letting people know when to rob them. I don’t want people to know where I am.”

And these innovations have taken years of constant attention to bring to their current state. And they are not done.

One Innovator’s Story

Dennis Crowley, founder of Foursquare, was in the room at Wherecamp in 2007 where I was giving a talk about location check-in habits via Twitter (a subject I knew well because of my Twittervision service, which allowed this.)

Dennis, of course, also founded the precursor to Foursquare, Dodgeball, which he sold to Google in 2004 (they promptly killed it.)

But Dennis wanted to see his vision come to pass, and he knew it would someday be possible — though at that point the iPhone had not been released and it would be nearly two years before it supported GPS location technology.

But there Dennis was, doing his homework in 2007, studying user behavior to figure out exactly what behaviors he would have to encourage to make Foursquare work.

He asked me, “so, people are really putting their home and work locations formatted inside tweets in order to update their location?”

“Yep, a few thousand times a day,” I replied.

“That’s cool. That’s really cool stuff,” he said. And from that, and years of similar evidence-gathering and study, Foursquare would be born.

So, creating Foursquare took about five years. (I could have “stolen” the idea and built Foursquare myself. But I didn’t execute on that; it was his vision to pursue.) Dennis did his homework. He was prepared. And his vision preceded the technology that enabled it.

Why, not How

Real innovation doesn’t come from a weekend. It comes from passion, years of study, understanding deep insights and the “why,” and persistence in seeing something new to market, along with the marketing and cheerleading that will make it successful.

The iPad owes much to Steve Jobs’ love of calligraphy. He cultivated a sense of aesthetics because of that initial interest. He didn’t set out to “make money” but rather dedicated himself to changing the world for the better using the entirety of his humanity. Time studying art wasn’t “lost,” it was R&D for the Mac, iPhone, and iPad.

Many of today’s entrepreneurs could stand to do less “hustling” and more reading, exploring, reflecting, and gathering input — and when it is time to make stuff, set their sights as high as possible.

There is more to this world than money, and there are countless opportunities to make it a vastly better place. Rather than using our CPU cycles just playing with combinatorial innovations, let’s devote ourselves to making the world as amazing as possible. Try to take time to reflect on how you can make the world better, and not just on what current technology affords.

Firesheep is a startling plugin that allows anyone to easily impersonate the login credentials of others for dozens of sites. It works on any unencrypted WiFi connection and is stupid-simple to setup. It can be done by anyone in a matter of minutes.

Just to illustrate how easy it is to setup, I was on Virgin America flight VX67 from Washington to San Francisco yesterday.

All I had to do to get going with Firesheep was download Firefox (onto my new MacBook Air) using the in-flight WiFi, and then download the Firesheep plugin for Firefox. Just drag the plugin into Firefox and it installs. Reload Firefox and you’re ready to go.

Click “Start Capturing” and you are instantly snooping on every interaction occurring on the WiFi network. In my case yesterday, that meant snooping on everybody who was using the WiFi on my flight.

What’s At Risk?

Within just a couple of minutes, I was able to impersonate 3 people on Facebook (updating their status, exploring friends, doing anything I wanted to – of course I didn’t). Twitter is also at risk. So is Gmail. And so is Amazon.

Access to Amazon is perhaps the most worrying. Once I realized I was in under someone else’s Amazon account, I quickly shut down Firesheep: this is some scary stuff. What if I had changed the shipping address for the account and done a one-click order on a $10,000 watch or a $2,000 plasma TV?

This was all at 37,000 feet in an airplane (and way more entertaining than SkyMall). Like taking candy from a baby.

Even More Shocking…

Later in the afternoon I was at one of the Internet Industry’s high-profile events: Web 2.0 Summit produced by O’Reilly. There on the hotel’s WiFi, which was setup to serve the summit, I ran Firesheep. Within seconds I had compromised about 25 accounts, including the Twitter accounts of O’Reilly Media and TechCrunch writer Alexia Tsotsis. Change passwords, tweet-as-them, friend and de-friend people? No problem. Here’s what I saw. (Note that my accounts were vulnerable as well.)

How It Works

I have not studied this exploit carefully enough yet to explain it in full detail, but my understanding is that on an open WiFi network, it’s trivial to capture in cleartext all of the web interactions of the users around you on the same IP network. Once you can do that (something Firesheep achieves using the pcap library, capturing port 80) then you can sniff for credential information specific to particular websites. Firesheep supports a couple of dozen out of the box, including all major social networking sites (Facebook, Twitter, Gmail, Gowalla, Foursquare) but also some more obscure sites relevant to coders (Github, Pivotal Tracker). Ouch. It even has an “import” function so others can write exploits for sites that Firesheep doesn’t know about yet.

The bottom line is that these sites all need to enforce the use of HTTPS (secure HTTP) rather than HTTP *before* the login handshake occurs. This will force some emergency changes by many sites over the next few days.

This is not a new exploit – it’s always been possible to do this; Firesheep just makes it stupid easy.

A Note On Passwords vs. Encryption

You’ve encountered WiFI networks that require WEP or WPA encryption passwords. These are secure from Firesheep’s reach. However, there are a lot of WiFi networks that require “passwords” (such as those at coffee shops, hotels, etc) that are in fact open networks. Many do not even require you to login to them to exploit them via Firesheep. To put it in perspective, every Starbucks location is vulnerable to attack.

The only for-sure ways to stay safe from Firesheep for now are to 1) use only encrypted WiFi networks (that use WPA or equivalent), 2) use wired networks that you trust. Any open WiFi network can and will be vulnerable to this attack until vulnerable sites switch to using HTTPS for all authentication. Be very careful out there, folks.

So, it’s a real dilemma. No one seems to be sure how to really address it other than to eliminate or curb the use of open networks, which is probably where it’s going to end up. So open WiFi is now basically over. Expect places that had been using it to post publicly available WPA passwords, which solves the problem.

I’m enjoying watching folks around the world prognosticate about the iPad, what it is and is not, how it might sell and what it means for computing. Sorry, but I can’t help but weigh in with some predictions.

My son (age 12) and I have a bet at the moment about the outcome of the NCAA basketball tournament, which I know nothing at all about: I wagered that Duke would emerge victorious (I ignored the rest of the brackets). If I am correct, he owes me $487 trillion dollars; otherwise I owe him $12. (Hey, I’m trying to teach him about Popperian philosophy.)

So, it is with the understanding that if I’m right, you, dear reader will owe me $487 trillion dollars, that I offer this humble marketplace analysis.

• iPad will be released on Saturday, April 3. That means that a ton of people are going to get to play with it over the Easter weekend. And I’m talking about peoples’ moms and aunts here. It’s been widely reported that the experience of using the device is quite seductive, and I’ve argued it’s because it activates different parts of the brain. Somewhere around 200,000 units will be sold over this coming weekend, and each one will be shown to an average of 10.6 other people, creating a latent (nagging) demand for another 21 million units.
• A bunch of old-media outlets will rejigger their offerings for the iPad and try to monetize the audience. Many already have. But this is Waterloo. Or Little Big Horn. They will sucker some folks into using the device for the “traditional” content, but sales will be disappointing. Ultimately they are going to have to radically reconsolidate their offerings and innovate in some serious ways. See below re: piracy.
• The device is going to continue to rip through the population, busting past all sales records for a general computing device. This will have nothing to do with features or even the apps (yet). This will be based on the user experience alone. Everyone who uses the thing comes away sounding like a religious convert. In the same way that the original iPod just “felt right,” Jony Ive has managed to bring meaning to a general purpose computing device like nothing ever before. The central thing Ive has done is to bring the experience of computing directly to the user, with no barriers and no “analog” devices like the mouse. People will have a visceral relationship with these devices.
• Roughly 20% of the initial batch of Wi-Fi only devices will be “handed down” to a secondary wave of users when the 3G models are introduced a month later. This will amplify the initial sales numbers, as many folks end up buying two units in the first month.
• PDF-format books and news will become the Lingua Franca. What happened to music and movies is about to happen to books. A wave of piracy will couple with a race to the bottom in content prices. Some killer app, possibly Kindle for iPad, will capture a big chunk of the market share. It doesn’t much matter how it plays out, but paper books are going to be items of “significance” and the kind of thing hipsters trade, like vinyl records.
• All desktop software will seem obsolete overnight. The obsessive attention Apple has paid to aesthetics in the built-in reader, calendar, and email apps will set the bar not only for other app developers on the iPad, but also for the iPhone and particularly the Desktop. Expect your Mac to feel particularly creaky. And Windows? It’s gonna seem steampunk compared to the twee aesthetics and colors emerging in the iPad design universe.
• WiFi is going to become even more ubiquitous and free. Businesses are going to trip over themselves to get iPad users into their establishments, as the iPad rides its way to prominence. WiFi-only iPads are going to be somewhat cooler than the 3G versions.
• Hipsters are gonna start using iPads as cell phones, using Skype and similar apps to bypass carrier relationships altogether. I’d expect the 3G-iPads to be used for voice too, marking the first significant use of the cellular network in a “data-only” mode, which will ultimately lead to the scrapping of the whole “voice/voicemail/minutes” paradigm. The first carrier to do this will have a temporary competitive advantage.
• A whole new market in mouseless/keyboardless computing will emerge. Yeah, I don’t know what it’s going to look like either. But the raw numbers (100 million by 2015) of the iPad platform will create a new kind of pop/tech culture. Expect a New York Times Sunday magazine piece; potentially in that publications’ last print issue.
• The next generation Macintosh, if there is such a thing, will be based on the iPad OS. Hard to say what this might mean, but I would not be surprised if Mac OS was phased out over a few years, or possibly converted into a server-only OS for the MacPro / X-Serve platform only.

Remember that demand is not static waiting to be filled by the possible universe of devices: if that were the case, the iPod and the Mac and the iPhone should never really have gotten any traffic. What Apple understands is that good design can change the market, and invent new markets.

And this is what the iPad will do: invent a new market. And the presence of that new market will profoundly change the dynamics of the existing (previous) market. New demand will emerge, and all kinds of new supply will emerge. The great thing about Apple, particularly Jobs and Ive, is that they know how to drive change.

And that, ultimately, is what entrepreneurship and innovation are all about. If it were just about building devices to match the demands of the existing market, the Chinese seem to do a pretty good job of that.

And I will supply my banking information, so you can wire me the money, when this all comes to pass. If I’m wrong, I’ll buy you a beer.

Twice last year, I had the experience of putting together SocialDevCamp East, a barcamp-style unconference for software developers and entrepreneurs focused on social media.

Sounds straightforward enough, but that sentence alone is jam-packed with important design decisions. And those design decisions carried through the entire event, and even into its long-term impact on our community and our community’s brand. I’ll explain.

Barcamp-Style Unconference

In the last few years, the Barcamp unconference format, focused on community involvement, openness, and attendee participation has gained a lot of traction. I won’t write a ton here describing the format and how it all works as that’s been done elsewhere, but the key point is that this is an open event which is supported by and developed by the community itself. As a result, it is by definition designed to serve that community.

So what are some other design implications of choosing the Barcamp format? Here are two big ones.

First, anyone who doesn’t think this format sounds like a good idea (but how will it all work? what, no rubber chicken lunch? where’s the corporate swag?) will stay away. Perfect. Barcamp is not a format that works for everybody – particularly people with naked corporate agendas. It naturally repels people who might otherwise detract from the event.

Second, the user-generated conference agenda (formed in the event’s first hour by all participants voting on what sessions will be held) insures that the day will serve the participants who are actually there, and not some imagined corporate-sales-driven agenda that was dreamed up by a top-down conference planning apparatchik three months in advance.

The fact that there are no official “speakers” and only participants who are willing and able to share what they know means that sessions are multi-voiced conversations and not boring one-to-many spews from egomaniacal “speakers.”

The Name: SocialDevCamp East

We could have put on a standard BarCamp, but that wasn’t really what we wanted to pursue; as an entrepreneur and software developer focused on the social media space, I (and event co-chairs Ann Bernard and Keith Casey, who helped with SDCE1) wanted to try to identify other people like us on the east coast.

We chose the word Social to reflect the fact that we are interested in reaching people who have an interest in Social media. It also sounds “social” and collaborative, themes which harmonize with the overall event.

We chose the wordlet Dev to indicate that we are interested in development topics (borrowing from other such events like iPhoneDevCamp and DevCamp, coined by Chris Messina). This should serve to repel folks that are just interested in Podcasting or in simply meeting people; both fine things, but not what we were choosing to focus on.

Obviously Camp indicates we are borrowing the Barcamp unconference format, so people know to expect a community-built, user-driven event that will take form the morning of the event itself.

We chose East to indicate that a) we wanted to draw from the entire east coast corridor (DC to Boston, primarily), and b) we wanted to encourage others in other places to have SocialDevCamps too. Not long after SDCE1, there was a SocialDevCamp Chicago.

Additionally, our tagline coined by Keith Casey, “Charting the Next Course” indicates that we are interested in talking about what’s coming next, not just in what’s happening now. This served to attract forward-looking folks and set the tone for the event.

The Location

We wanted to make the event easily accessible to people all along the east coast. Being based in Baltimore, we were able to leverage its central location between DC and Philadelphia. Our venue at the University of Baltimore is located just two blocks away from the Amtrak train station, which meant that the event was only 3 hours away for people in New York City. As a result had a significant contingent of folks from DC, Baltimore, Wilmington, Philadelphia, New York, and Boston, many of whom came by train.

Long Term Brand Impact

These two events, held in May and November 2008, are still reverberating throughout the region’s community. At Ignite Baltimore on Thursday, SocialDevCamp was mentioned by multiple speakers as an example of the kind of bottom-up grassroots efforts which are now starting to flourish here.

The event has the reputation of having been a substantive, forward-looking gathering of entrepreneurs, technologists, and artists, and that has gone on to color how we in the region and those in other regions perceive our area. Even if it’s only in a small way, SocialDevCamp helped set the tone for discourse in our region.

Design? Or Just Event Planning?

Some might say that what I’ve described is nothing more than conference planning 101, but here’s why it’s different: first, what I’ve described here are simply the input parameters for the event. Writing about conference planning would typically focus on the logistical details: insurance, parking, catering, badges, registration fees, etc. Those are the left-brained artifacts of the right-brained discipline of conference design.

Everything about the event was designed to produce particular behaviors at the event, and even after the event. While I make no claim that we got every detail perfect (who does?), the design was carried out as planned and had the intended results. And of course, we learned valuable lessons that we will use to help shape the design of future events. Event planners should spend some time meditating about the difference between design and planning; planning is what you do in service of the design. Design is what shapes the user-experience, sets the tone, and determines the long-term value of an event.

More to Come

I’ve got at least 3 more installations in this series. Stay tuned, and I’d love to hear your feedback about design and how it influences our daily experience.

WARNING – GEEK/PHILOSOPHER CONTENT:  It occurs to me that the universe is a kind of finite-state automaton, and as such is a kind of deterministic computing machine. (No, I was not the first to think of this.) But if it is a kind of computer, then design is a kind of program we feed in to that machine. What kind of program is it? Well, it’s likely not a Basic or Fortran program. It’s some kind of tiny recursive, fractal-like algorithm, where the depth of iteration determines the manifestations we see in the real world.

As designers, all we’re really doing is getting good at mastering this fractal algorithm and measuring its effects on reality.

See you in the next article!

At Xerox Parc in the 1970′s, Alan Kay fostered the innovations that form the foundation of modern computing. Windowing, mice, object oriented languages, laser printing, WYSIWYG, and lots of other stuff we take for granted today either had its start or was fleshed out at Xerox Parc.

The venerable mouse, which enabled direct manipulation of content on the screen, was just one of a few innovations that was screen-tested as a possible heir to the venerable cursor and text terminal metaphor which had predominated since the dawn of computing.

Mice, trackballs, light pens, tablets, and Victorian-looking headgear tracking everything from brainwaves to head and eye movements were all considered as the potential input devices of the future. No doubt there were other metaphors besides windows considered as well. Hypercard, anyone?

Steve Jobs, by selecting the mouse as the metaphor of choice for the Lisa and subsequent Macintosh computers, sealed the deal.  Within a year, Bill Gates, by stealing the same design metaphor for use in Windows 1.0, finished the deed.  By 1986, the mouse was a fait accompli.

Since the dawn of the Mac and Windows 1.0, we’ve taken for granted the notion that the mouse is and will be the primary user interface for most personal computing and for most software.

However, computing is embedded in every part of our lives today, from our cell phones to our cars to games and zillions of other devices around the house, and those devices have myriad different user interfaces.  In fact, creating new user experiences is central to the identity of these technologies.  What would an iPhone be without a touch screen?  What would the Wii be without its Wiimotes?  What, indeed, is an Xbox 360 but a PC with, uh, lipstick and a different user interface metaphor?

(An aside: How awesome would it be if the iPhone, Wii, and Xbox 360 all required the use of a mouse?  People fidgeting on a cold day, taking out their iPhone, holding it in their left hand, plugging in their mouse, working it around on their pants to make a call.  Kids splayed out on the rumpus room floor, mousing around their Mario Karts. Killer, souped up force-feedback mice made just for killing people in Halo.  Mice everywhere, for the win.)

So, what’s with the rant?  Simply that the web has taken a bad problem — our over-reliance on mice — and made it even more ubiquitous than it was in the worst days of windowing UI’s.

“And then if you click here…”

No, here — not over there.  Click here first.  Scroll down, ok, then click submit.  Now click save.

See the problem?  The reliance on the mouse metaphor on the web is fraught with two hazards.

1. Mice require users to become collaborators in your design.
2. Each user only brings so much “click capital” to the party.

Catch My Disease

We’ve all had the experience of using a site or app that requires a great deal of either time or advance knowledge to fully utilize.

You know the ones — the ones with lots of buttons and knobs and select boxes and forms just waiting for you to simply click here, enter the desired date, choose the category, then get the subcategory, choose three friends to share it with, then scroll down and enter your birthdate and a captcha (dude) and then simply press “check” to see if your selection is available for the desired date; if it is, you’ll have an opportunity to click “confirm” and your choice will be emailed to you, at which point you will need to click the link in the email to confirm your identity, and you’ll be redirected back to the main site at which point you’ll have complete and total admin control over your new site.  Click here to read the section on “Getting Started”, and you can click on “Chat with Support” at any time if you have any questions.

What the hell do these sites want from you?

If these sites are trying to provide a service, why do they need you to do so much to make them work?  Sure, some stuff is complex and requires information and processes and steps to empower them, but when you ask users to participate too much as key elements in your design, you create frustration, resentment, and ultimately rage.  That’s cool if that’s your goal, but if you’re trying to get happy users, you’ve done nothing to advance that cause.  So, it shouldn’t be about “all you have to do is click here and here.” Ask less of your users.  Do more for them.  Isn’t that what service is all about?

Limited Click Capital

Sometimes, people just want to be served — even entertained or enchanted. They don’t want to become the slavish backend to a maniacal computer program that requires 6 inputs before it can continue.  Is the user in service of the computer, or is the computer serving the user?  I always thought it was the latter.

I’ll never cease to be instructed by the lessons learned from developing my sites Twittervision and Flickrvision. Both sites do something uncommon — they provide passive entertainment, enchantment, and insight in a world where people are asked to click, select, participate, scroll, sign up, and activate. It’s sit back and relax and contemplate, rather than decipher, decide and interact.  Surely there are roles for both, but people are so completely tired of deciphering, that having a chance to simply watch passively is a joyful respite in a world of what is mostly full of badly designed sites and interactions. This alone explains their continued appeal.

People come to sites with only so much “click capital,” or willingness to click on and through a site or a “proposed interaction.”  This is why site bounce rates are usually so high.  People simply run out of steam before they have a chance to be put through your entire Rube Goldberg machine.  Make things easier for them by demanding fewer clicks and interactions.

Make Computing Power Work For Your Users

Truism alert: we live in an age with unprecedented access to computing power.  What are you going to do with it?  How are you going to use it to enchant, delight, and free your users?  Most designs imprison their users by shackling them to the design, turning them into nothing more than steps 3, 6, 8, 9, and 11 of a 12 part process.  How are you going to unshackle your users by making them — and their unfettered curiosity — the first step in a beautiful, infinitely progressive algorithm?

Predict and Refine

Forms and environments that rely on excessive interaction typically make one fatal assumption: that the user knows what they want. Most users don’t know what they want, or they can’t express it the way you need to know it, or they click the wrong thing.  Remove that choice.

Do your best to help your users along by taking a good guess at what they want, and then allow them to refine or steer the process.

Remember, you’re the one with the big database and the computers and the web at your disposal: how are you going to help the user rather than asking the user to help you?  You’re advantaged over the user; make it count for something.

Don’t Think About Mice

Mice lead to widgets. Widgets lead to controls. Controls lead to forms. Forms lead to hate. How are you going to break free from this cycle and give your users something compelling and useful with the minimum (and most appropriate) interaction? What is appropriate interaction?

It depends.  What if you rely on gestures, or mouseovers, or 3 yes or no questions in big bold colors?  That’s minimal and simple.  It  may be just what you need to empower your idea and serve your users.

I’ve been working with the WiiMote and the iPhone a lot lately, and trying to use touch screens, accelerometers, and the Wii’s pitch and roll sensors to create new kinds of interaction.  Maybe this is right for your work.

Think about it and don’t assume traditional mouse/web/form interactions. Sure, sometimes they are the right and only tool for the job, but if you want to stand out and create compelling experiences, they surely can no longer be the central experience of your design.

Long Live the Cursor

Back in the early days of GUIs, there were lots of people who contended that no serious work would ever get done in a window and that the staple of computing and business would be the DOS metaphor and terminal interactions.  There have been dead-enders as long as there have been new technologies to loathe.  I’m sure somewhere there was a vehement anti-steel crowd.

The mouse, the window, and HTML controls and forms are the wooden cudgels of our era — useful enough for pounding grain, but still enslaving us in the end.  How will you use the abundance of computing power, and new user interface metaphors to free people to derive meaning and value?

Boulevard St. Michel, Paris, Google Streetview

So many wonderful things going on in this photo, and it’s all entirely unintentional. With such a vast quantity of visual data collected for Google Streetview, how many “artistic” scenes lurk within it?  How might one build a machine for finding the art within this dataset?  Can it be crowdsourced?

Want to work on this with me?  If so, ping me.

In September, I had the opportunity to hang out with Alex Hillman in Vienna, Austria at the wedding of our mutual friends Amy Hoy and Thomas Fuchs, and while Alex and I had peripherally known of each other, we hadn’t had a chance to actually meet and talk.  It turned out we were both staying at the same hostel, and as a result we had a chance to talk about a bunch of stuff from projects to Alex’s pioneering work in developing coworking at IndyHall in Philadelphia.

I’d known about coworking and its evolution since 2007; in fact I talked with Noel Hidalgo on video about the concept in Berlin in July 2007, along with Travis Todd, but while I liked the idea of coworking I didn’t really have a way to put it in practice yet.

Well, after seeing events like SocialDevCamp, Ignite Baltimore, and TwinTech take root here in the Baltimore area, it became clear to me that the time was also ripe for coworking in Baltimore. As I shared the idea with friends and colleagues, it was clear that we could build momentum around the concept quickly.

So, on Saturday and with Alex’s help, we held a session on coworking at SocialDevCampEast2, and we went over the key concepts behind coworking, answered some questions, and by the end of the session had created a mailing list.  Yesterday we held the first “official” Baltimore coworking session at Bluehouse, and we expect to keep that up every Tuesday and Thursday until we establish a more permanent home.

Of all the insights that Alex has gained in running IndyHall, I’d say this is the most important: “If IndyHall, as a place, ceased to exist tomorrow, IndyHall would still exist as a community.”  And this is truly key. Too often, people get distracted with the particulars of a piece of real estate or a locale or amenities; none of that is central to the mission.  The most important thing is the community and the ideas they share. There will always be a place where that community can take root.

That being said, we are looking at various ways to give coworking in Baltimore a more permanent home, and we have a bunch of ideas about how to do that.  If you would like to be in on that conversation, I invite you to join the Coworking Baltimore Google Group.  And of course, stop by Bluehouse next week on Tuesday or Thursday, between 10am and 4pm!

Feel free to contact me with ideas or questions about coworking and how we can establish a sustainable, vibrant creative community here in Baltimore! I’m really looking forward to working with all of you.

I’m finally recovered after a really exhausting week that included SocialDevCamp and the wild ride of Twitter Vote Report.

SocialDevCampEast2 went off without a hitch on Saturday at University of Baltimore.  Once again, some of the best and brightest developers, entrepreneurs and social media gurus gathered to trade ideas and talk about the future of the web.

One thing we try to do at SocialDevCamp is vote on the sessions, to make sure they are things that people really want to hear about, or at least size the discussions to the right rooms.  We ran 5 rooms all day in 5 sessions plus lunch, for a total of 25 sessions! Check out the wiki to see the sessions that were held.

Personally, I enjoyed the conversation on location technology, and why location-based social networks have yet to reach critical mass.  Most folks felt that there was a technological barrier — it’s just too hard to continuously update your location with current device and battery constraints — and others questioned what incentives people have to update their locations.  We decided that those incentives probably needed to be tuned in order to see a successful location-based service emerge, and that there may also be benefit for people sharing location-related information anonymously.  Great talk, and I’m still thinking about what incentives might make LBS actually work.

We did a session on Twitter Vote Report, which was awesome because we were actually able to recruit some members of the crowd to do some work on the project!  Bryan Liles and John Trupiano contributed some great work to the codebase, some while sitting in the session!  We talked about the overall architecture of the project, and the fact that it was put together in just two short weeks of coding!

There was a good conversation about iPhone development, introducing people to the platform and answering questions about the platform.  Many seemed to be glad to get a feel for Cocoa and I wouldn’t be surprised if several of the folks there end up working on the platform!

Alex Hillman of Philadelphia’s Indy Hall helped to lead a discussion on co-working in Baltimore, and by the end of the session, we had actually launched co-working in Baltimore, with a mailing list and a set of great ideas for taking things forward.  Yesterday, we held our first “official” co-working meetup at Bluehouse in Baltimore; I’ll write more about the co-working initiative separately.

Because I wasn’t in the other sessions, I can’t say what all was said in them, but I heard good things about the conversations on data portability, source code management with Git, and crowdsourcing. If you were in one of the sessions, feel free to leave some comments here or links to your own blog!

Ann Bernard helped put together an awesome party for SocialDevCamp at Metro Gallery with great food from Tapas Teatro and an open bar.  And live music from Natasha El-Sergany, KADMAN, and Ra-Ra-Rasputin… A great way to end the day, and I can say that by the time it was all over, I had talked to a few hundred people and was completely exhausted!

This morning, Mike Subelsky, a friend and one of the organizers of the recent and fabulous Ignite Baltimore said via email, “It is not an exaggeration to say that SDCE has totally changed my life,” referring to the first SocialDevCamp held in May. Not to sound self-congratulatory, but the same is true for me.

SocialDevCamp is one of a few things sparking a renaissance here in the Baltimore/Washington area, giving rise to events like Ignite and to movements like co-working.  With the social media tools available now, this sort of thing is finally possible to do, and it’s hugely gratifying to see it happening!

See you next spring for SocialDevCampEast3!

Being busy seems to always come in spurts for me… just when it looks like I’ve got too much to do already, something cool turns up and takes things to whole new level of busy.

That would be this week. SocialDevCamp East, the barcamp-style unconference that I started with some friends last spring is back tomorrow, and that’s certainly required some coordination and planning.  That would have been plenty.  We have over 200 RSVP’s now (between the Wiki and Facebook) and we expect a truly incredible day of networking and learning.  See you tomorrow!

The other big news of the last two weeks has been the TwitterVoteReport project, for which I’ve been acting as defacto CTO since about October 18th.  This is a great project, a great cause, and an awesome idea.  The data we collect will be an archival quality primary source document for future generations to study the evolution of the election process.

We have five distinct data sources coming in about people’s experience at their polling places: Twitter, Telephone, Direct SMS, and Apps for Android and iPhone.  These are all normalized and aggregated into a single database and reviewed by humans for maximum accuracy.  The data will then be made available in real time to anyone who wants it — from the media to watchdog groups to mapmakers — to help the world understand and monitor the 2008 US elections.

Putting this project together, with all these diverse inputs, has been a monumental task and a real demonstration of what’s possible when people decide to work together.  We had over 600 phone channels donated.  We were able to think up, code, and submit an iPhone app in just 3 days.  We’ve received press coverage far and wide from sources as diverse as TechCrunch and Fox News.  Not bad for a few days’ work.

There’s plenty more to do still (between now and Monday), and I’m busy all day tomorrow at SocialDevCamp.  We’ll do a session there on TwitterVoteReport and what we’re up to… we still need more help from people good with maps!

I’ll post more here as things evolve, and a recap next week, but remember, nothing’s impossible when caring people dedicate themselves to a common endeavor.

Meantime, check out:

• http://twittervotereport.com
• http://votereport.pbwiki.com
• http://socialdevcamp.net

For too long, the educated class has held an unspoken compact: nerds, you worry about computers and gadgets and Battlestar Galactica; dreamers, you worry about art and experimental thought and the environment and plants and music.  And generally speaking, the less these two crowds had to see each other, the happier they tended to be.

This was OK in an era like the 60′s where, for the most part, computing was best reserved for invoices, and fine art had little to do with math. The computer guys were needed to figure out hard implementational problems: how to store all those invoices and be sure the numbers were right, or the math behind making sure a rocket flew straight. Good, tough problems of the era, to be sure, but almost entirely orthogonal to the guys dreaming up the tailfins on the cars and the ads that sold them. Think about the role of geeks in era-pieces like Mad Men and The Right Stuff and you get an idea of how oil-and-water these crowds were.

Fast forward to today, where computers are a creative instrument capable of fine-art quality interaction in multiple media: video, still photography, sound, music, animation, visualization, and even the creation of physical interactions and physical objects.  3D printing, computer controlled robots and art machines, physical art installations of awesome complexity, and autonomous digital art objects are not only possible, but they are accessible to average people who simply want to create. We have truly entered an era where the walls between technical and creative have been razed, however if we fail to realize it and move past them, we may find ourselves constrained by an older notion of what’s possible.

As an example, I’ll take last night’s Ignite Baltimore #1, at which I was proud, honored (and a tad nervous) to be speaker #1. The topics covered were vast and varied, and I’d argue were just the kind of fuel that Baltimore’s creative class needs as input as we set off to solve the challenges of the next 50 years. The topics, in no particular order: public transportation, urban gardening, public spaces, the bible, web apps, agile development, 100 mistakes, cognitive bias, east coast industrial landscapes as art, radio stories, writing vs. speaking, entrepreneurial experience, and much more.

I’d argue that this is the kind of wide ranging liberal arts discussion that most nerds would have opted out of in the past, and that nerds would not be the preferred audience of the dreamers, artists, and poets.  The magic of today, however — the true genius of the moment here in 2008 — is that this cross-fertilization is finally starting to happen. And freely and with passion. Why? Because these walls between creativity, art, science, and math, have finally started to wear down — and not just in some university’s interdisciplinary studies department — but in popular culture and conceptions. The mashup is now considered not just a valid art form, but a standard process for solving today’s toughest problems.

Creative thought has achieved primacy. It is now the idea that matters, because when the idea is properly and fully conceived, the design, presentation, and implementation are necessarily correct as well. What do I mean by this? If there is total integration between the processes of ideation and implementation, there is simply no separation between an idea, the thought models that underly it, and its implementation in digital form: they are one.

It used to be that there was a wall between a digital implementation and an idea; a digital implementation would involve “hacks” — making stuff work in spite of memory or display or other limitations — and the computer-enabling “portion” of a solution would be some subset (usually a rather compromised subset) of an overall idea.

Today, object oriented programming and database technology make it possible to model a solution end to end with few compromises; so, in fact, digital implementers become full partners in the design conversation, greatly eliminating waste, and empowering programmers creatively. Agile development practices (involving iteration rather than top-down design) and story-based development (giving non-programmers a “narrative” to follow about the “story” of their solution) make it so there is very little distinction between design, programming, and ideation. They are now effectively the same disciplines.

And this explains why so many have argued that we are entering a new era of the right brain and of the “rise of the creative class.” The fact is if any of this had been possible sooner, it would have happened sooner. Generally speaking, people don’t like being pigeonholed into some tiny specialty, or to have their thinking constrained. We are human; all of our brains have two halves. But for too long, we have all likely underutilized one side or the other.

So, now we are all free; now, united with better tools and better processes, it is time to turn our attention to the hard, human problems of our age: energy, hunger, the environment (built and natural), and meaning, to name a few. And the topics at last night’s Ignite Baltimore were just the right fuel for getting us started thinking about these hard problems.

Kennedy famously said that “we choose to go to the moon… not because it is easy, but because it is hard.” Our generation needs to start to figure out how to apply the massive wealth of talent (and newfound technical+creative skills) to the truly hard problems of our age.

It’s not going to happen overnight, and we all don’t need to go out and start wind power companies.  But, we all must make ourselves open to BOTH sides of our brains. We must realize that it is poetry and art which will provide the insight we need to make technical breakthroughs. We must listen to each other and be open to diverse viewpoints. We must become spiritual beings — it doesn’t matter whether your spirituality comes more from The Force than The Bible or The Koran – but to deny oneself any of the channels of thought that inform our basic human nature is to cut yourself off from the great insights and genius of one’s humanity.

Be open. Listen to people. Look at diverse kinds of art. Listen to diverse kinds of music. If you want to take part in the next great wave of innovation, these are the kinds of fuels you’ll need to do it.  And I hope to see you at the next Ignite Baltimore in February 2009, where we can continue this conversation!