Facebook’s Open Compute Project On a large scale like this — not a small open-source project by good-willed individuals — “opening” something is almost always an effort to commoditize it, leveling the playing field as much as possible and marginalizing competitive advantages that others might have had. [..] Nobody “opens” the parts of their business […]

Talking to Jekyll using MarsEdit

Brent Simmons wrote a plea for Baked Weblogs the other week. It resonated – I’m the sort of nerd who obsessively re-writes his blogging engine more often than he actually uses it to blog things with, so I’ve been through a lot of solutions, and I keep coming back to baking. Anyway. Brent wrote another […]

titles as metadata

Are titles on blog entries good things or not? I’m feeling an obligation to give things I write a title. But nowadays this is mostly because it forms a useful bit of text to use as a link target. Without a title, I have to excerpt the first few words of a piece, which always […]


There have been a couple of things I’ve been linked to recently about how some APIs claim that they are RESTian, but aren’t really – Gareth and Jens. To my mind, there’s not a lot of clarity here. So. Things that make your web service RESTian: Resources are represented by URLs. Resources can be cached […]

Opinions on REST

I wrote a thing about what is and isn’t REST. That was (what I believe are) the facts. This bit is opinion. Things that actually matter: You’ve shipped something. Your API has client libraries, even if they’re trivial wrappers (because people will complain otherwise, or write bad ones). REST is a nice dream. But I’m […]

Every response should contain hyperlinks to other resources, where the structure/metadata around it indicates what’s on the other end. It should still be self-describing even if the URL is completely opaque — “nice URLs” do not make you RESTful. You should never need an “endpoint” or any documentation at all, whether machine or human-readable. I […]