Manifesto’s are quite popular in the tech community — obviously there’s the agile manifesto and I’ve written before about the kaizen manifesto and then there’s the Manifesto for Software Craftsmanship. They all try to put forward a way of working, a way of raising professionalism and a way of improving the quality of what you do and build.
Anyway when we started work on on the BBC’s Nature site we set out our development manifesto. I thought you might be interested in it:
- Peristence — only mint a new URIs if one doesn’t already exist: once minted, never delete it
- Linked open data — data and documents describe the real world; things in the real world are identified via HTTP URIs; links describe how those things are related to each other.
- The website is the API
- RESTful — the Web is stateless, work with this architecture, not against it.
- One Web – one canonical URI for each resource (thing), dereferenced to the appropriate representation (HTML, JSON, RDF, etc.).
- Fix the data don’t hack the code
- Books have pages, the web has links
- Do it right or don’t do it at all — don’t hack in quick fixes or ‘tactical solutions’ they are bad for users and bad for the code.
- Release early, release often — small, incremental changes are easy to test and proof.
It’s worth noting that we didn’t always live up to these standards — but at least when we broke our rules we did so knowingly and had a chance of fixing them at a later date.