Accountability moment: not one more gay cent until we see some results

When politicians make promises, they should be held to them. Especially when they promise hope, a new kind of politics, that they want to take contributions from actual people and be accountable to them. Well, we heard lots of promises, but we've not seen any action. Until we start seeing the change we paid for, President Obama and the Democratic party can forget about getting any more of my money:

I pledge not to donate to the Democratic National Committee, Organizing for America, or the Obama campaign until Congress passes, and the president signs, legislation enacting the Employment Non-Discrimination Act (ENDA), repealing Don't Ask, Don't Tell (DADT), and repealing the Defense of Marriage Act (DOMA).

And yes, I'm serious about this. You'd better believe corporate donors are getting their money's worth right now, as they belly up to the trough for "healthcare reform". If they don't get what they paid for, they're not going to give again – and guess what, neither am I.

Both DOMA and DADT were passed during the previous Democratic administration. The just-finished Bush administration produced plenty of sturm und drang about teh gays, but never actually did legislative harm to us. The Obama administration had better start righting some wrongs, and President Obama had better start doing something to fulfill his pledge to be a "fierce advocate" for our community. With sixty filibuster-breaking votes in the senate and a strong majority in the house, the Democratic party has an opportunity to actually pass the agenda they trumpet when they come around begging for cash. With the midterm elections coming the time to act is now; otherwise it becomes increasingly obvious that the Democratic party is determined to block action on these issues in order to keep the gay money coming.

Either put up or find another sucker. If you feel the same way, join me in the pledge.

The cross-species dinosaur team meets to discuss the ideal design for a mammal

Distributed is the new Object Oriented

In the 80s, Object Oriented development promised a fundamental reshaping of the software development landscape, and it had distinct religious overtones. (You can tell it was religious because Object Oriented is capitalized.) It was going to be better in every way from procedural programming - everything would be reused, bugs would be eliminated, and mass love would result. Like Theravada Buddhism, once you accepted the Four Noble Truths of Encapsulation, Inheritance, Polymorphism, and Modularity everything else followed. This fever gripped the development world for twenty years, and thousands of developers never made the mental shift necessary to embrace it.

Leaders often made the fateful decision to rewrite existing procedural apps in object oriented technologies. Did the resulting programs run better? Um, no. Did they conquer the marketplace? God no. Did they run faster? Hell no. Windows Vista is a prime example; I'm not going to rehash any personal case histories because the pain is still too great. I'll let you know when I'm strong enough to cry.

Distributed development is as different from Object Oriented as Object Oriented is from procedural development. Most of the existing cadre of developers will never get this stuff, just as most procedural developers never figured out OO. Hadoop / MapReduce and Erlang require a rethinking of how problems should be solved, and a rethinking of what problems can be solved. Instead of figuring out how to best rewrite yesterday's apps with today's technologies, it's much better to treat them as solved problems and move on.

Vancouver's Open Data, Open Standards, Open Source and the Vancouver Public Library

Vancouver has adopted a policy of Open Data, Open Standards, Open Source and I'm really excited about it. David Ascher presented on the topic at Open Web Vancouver 2009 and pointed out that if we don't engage the city and use this data it will go nowhere.

The Vancouver Public Library is one of my favourite places. I love libraries, I love books, but the library here in Vancouver is a really special library for me. So I've been thinking of ways that the library could share data so that I could build applications to make the library more interesting and more valuable to the people of the city.

Here's some data I'd like to have:

• Books on order

  I'd like to know what new books are currently on order, but not available. I want a preview of coming attractions.

• Most unpopular books

  What doesn't get checked out? What's likely to get sold in the next round of disposal, ahem, book sale?

• Most popular books

  What's everybody reading?

• Top 100 sites for library patrons

  What are the most popular sites browsed from the library? I'd like to be able to contrast this with the most popular sites according to Alexa. That should help tell the library what sorts of services patrons need.

These are things that I could mash up into interesting applications, such as presenting a unified view of new popular books on Amazon and which ones are in the library, or popular in the local community.