Entries Tagged 'baltimore' ↓

As many of you know, I live along the shores of the Severn River, a river along the Chesapeake Bay, near Annapolis, Maryland.

This infuriating (but unsurprising) article in the Washington Post suggests that the metrics of its supposed cleanup that have been taking place the last 25 years have been inflated to reflect more progress than has in fact been made.

Just as the advice to an alcoholic on how to lose weight and get back to a normal lifestyle can be nothing other than “stop drinking,” the remedy for the bay is equally stark, though more complex. And the brainless consumer squads inhabiting the Chesapeake Bay watershed want to try every imaginable remedy other than the ones that will work.

If you want to fix the Chesapeake Bay, here’s how:

1. Offer massive tax credits for allowing industrial farmland to revert to forestland
2. Tax fertilizer sales
3. Offer tax credits for replacing industrial farms with grass farms
4. Discontinue commercial Blue Crab and fish harvest in the bay; yes, screw the watermen and end the industry
5. Tax all impermeable surfaces; tax large impermeable parking lots at a 4x rate
6. Use the impermeable surface tax to fund a tax credit for those installing permeable surfaces
7. Invest funds in stormwater and sewage handling plants
8. Price water at 5x its current price
9. Offer tax credits for commuting via bike and public transportation
10. Tax credits for people who place land under conservation easement

Got the theme here? It’s all about taxes. While I am not in favor of taxing people, I’m also not especially in favor of large scale programs to modify human behavior. This, however, is exactly what the people say they want, and there’s no surer way to change human behavior than with incentives and disincentives. Taxes and tax credits are arguably the only direct tool that government has to create such incentives for behavior change.

If at least a good portion of these measures are not undertaken (or ones which very much resemble them), I can only assume that — like the drunk who will try every other remedy other than to stop drinking — we are not serious about saving the Bay at all.

Which makes me wish people would shut up and get about their hurried destruction of it; it is the only intent we can infer from the behavior we see. Pave the Bay never sounded so realistic. It really seems as though no one — no one with the will to make a difference — really cares to solve the problem. And I blame us citizenry first and foremost, because we won’t give our elected officials the political cover to do any of the things that it would take to actually solve the problem.

In the circles I move in, there’s been a lot of discussion lately about Starfish and Spiders; reference to the 2006 book by Ori Brafman and Rod Beckstrom.

The idea behind the book, which I have not read (why should I have to fund these guys just to understand their point), is that top-down command and control style organizations resemble a spider, and that if the head of the spider is removed, the organization dies.

A starfish organization, in contrast, can survive damage, and in fact after one of its arms is severed can not only repair the arm, but the severed arm can re-grow a new body. Nice enough analogy, and good for getting the point across to thick-skulled CEO’s still mourning the apparent loss of their cheese.

However, I find the analogy a bit weak; the “starfish” concept doesn’t actually explain a lot of the behavioral properties that underlie “starfish” organizations. Folks in the coworking community rightly believe that it is a starfish-style movement: leaderless and self-healing.

Flocking behavior (as seen with birds and insects) is a more instructive analogy to me. On first glance, many naïvely assume that flocks follow a leader. Not true. Individual members of a flock obey just three simple rules, and this is all that’s required to produce complex flocking behavior:

• Separation: Steer to avoid crowding local flockmates
• Alignment: Steer towards the average heading of local flockmates
• Cohesion: Steer to move towards the average position of local flockmates

Quoting from Wikipedia (so it must be true), “In flocking simulations, there is no central control; each bird behaves autonomously. In other words, each bird has to decide for itself which flocks to consider as its environment. Usually environment is defined as a circle (2D) or sphere (3D) with a certain radius (representing reach). A basic implementation of a flocking algorithm has complexity O(n²) – each bird searches through all other birds to find those who falls into his environment.”

The implementation of coworking is flock-like. The spread of coworking is starfishy.

The reason why so many people have trouble defining coworking is because it defies centralized control, or the notion of a flock leader.  The reason why people say, “the only way to understand coworking is to do it,” is because it is fundamentally a flocking behavior which relies on individual execution of the flocking algorithm rules.

Flocking also explains why so many coworking environments end up selecting for the right people, with no defined rules or central control; each bird chooses whether the environment is right for her. The flock self selects.

So, if you’re having trouble explaining why your local coworking group has anything to do with starfish, maybe it’s time to start talking about your flock instead.

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!