The Dawn of the Municipal Chief Innovation Officer

Emily Badger in The Atlantic recently wrote about “The Dawn of the Municipal Chief Innovation Officer”. Technically Philly had a conversation with Philadelphia’s Adel Ebeid, Philadelphia’s first Chief Innovation Officer, back in November last year:

“There’s this one side of the coin where people see just this disenchantment and negative view of government,” says Jay Nath, the Chief Innovation Officer for the city of San Francisco. “But there’s also this flip side where people actually believe that working with government, we can make a better solution and better improvements for our society.”

…There are, by our count, just two major cities in the U.S. that currently have someone sitting in this role, and they’ve both settled in within the past six months. Adel Ebeid stepped into the job in Philadelphia after working as the chief information officer for the state of New Jersey. Like Nath, he views his role largely as connecting city hall and all of its resources with a new generation of problem-solvers outside of it.

…The birth of the municipal chief innovation officer job is a response to these two trends: to fundamental changes in technology that are revolutionizing citizen engagement, and to a cultural movement that is turning the data-dense inner workings of city halls into public challenges that are actually kind of a kick to solve.

“There aren’t that many of us right now,” Ebeid says, “but I can tell you we’re certainly an early testbed for what will become mainstream by 2015.”

Related:

City of Philadelphia: Office of Innovation and Technology

Talk: “The Web Browser is a Transitional Technology”

Allen Wirfs-Brock, a Mozilla Research Fellow, at YOW 2011, defined what he considers the current era of computing, and some exciting elements of where we are and where we are going in his talk “The Web Browser is a Transitional Technology”.

It looks like YOW 2011 had some fantastic talks to check out.

Al Sweigart: “Nobody Wants to Learn How to Program”

Author of “Invent with Python”, Al Sweigart, makes the case for teaching programming skills while enabling children to accomplish something, like making a game, not as an end in and of itself, in “Nobody Wants to Learn How to Program”. I believe this is mostly true, and the sooner we approach K-12 CS education similarly the better.

Steve Klabnik: Nobody Understands REST or HTTP

Steve Klabnik outlines some best practices in API design in “Nobody Understands REST or HTTP”, some of which I admit I need to follow more consistently. As he states in the end:

Seriously, most of the problems that you’re solving are social, not technical. The web is decades old at this point, most people have considered these kinds of problems in the past. That doesn’t mean that they always have the right answer, but they usually do have an answer, and it’d behoove you to know what it is before you invent something on your own.

Good article with clear to use tips.