This was ultimately the question that focused my mind when asked to write the manifesto. I wanted a top down view of the our development practices and direction, something that could be bundled up and documented.Why do we do it?

This was ultimately the question that focused my mind when asked to write the manifesto. I wanted a top down view of the our development practices and direction, something that could be bundled up and documented.

After many draft attempts (screwed up and thrown at the rubbish bin), ‘Why do we do it?’ kept coming back at the center of mind maps and other attempts to crystallize my thinking.

The point of this manifesto was to allow us all to use it as a framework to make decisions that affect the technical direction of the products. I also knew I had to keep it short and sweet. And here it is;

‍

This seems like common sense, are we not meant to be doing this anyway, but baked into this simple statement are a number of trade offs, that if we can master will take us to the height of our craft.

And this is what makes it worth pursuing. It means we can build our customers what they need in such a way that everyone’s proud of what has been created.

In future blog posts I’ll unpack our technical manifesto in more detail and explain why I think it’s worth pursuing.

‍