{ "blyg": "0.4", "id": "36627xna98agxt6qkyfgjta4nh", "kind": "thread", "origin": "https://notionparallax.co.uk/", "page": "https://notionparallax.co.uk/2015/a-manifesto-for-data-collection", "author": { "name": "Ben Doherty", "url": "https://notionparallax.co.uk/" }, "created": "2015-08-23T21:01:34Z", "updated": "2015-08-23T21:01:34Z", "version": 1, "content_md": "# A manifesto for data collection\n\n\n

This is something I spend a lot of time thinking about. That means I've developed some opinions!

\n

Andrew Godwin and Matthew Blair asked me to write a bit of a manifesto that explains what I think we should be thinking about. Read the posts below in any order, but this one first.

\n

_I'll add a disclaimer too. These are my opinions, not BVN policies!_

\n

Data is a huge subject. It's also something that, traditionally, architects aren't trained to deal with or understand[1. The obvious question (to Barry, I didn't think of it) is _who does feel comfortable with lots of data?_ Lots of professions need to deal with data: Psychologists, business people, statisticians, bookies, dog breeders, advertising, marketing, stock market traders... and more and more professions are being added to that list as a quantitative understanding of the world becomes a core of their business]. The main thrust of this manifesto is that we should be **bold**, **responsible** and **flexible**.

\n

What do I mean when I talk about data in this series? I'm talking about the things that go into the people and project pages and into timesheets. There are lots of other ways that we make data, and these are all important but I'll deal with them later on.

\n

Bold in that we should do brave things. We should be as open as possible with our data[1. this is a post, but it's still internal. I might post it one day]. We should set precedents by defining and controlling the API for our company and our industry.

\n

Responsible by having no admins and taking control over your own data. And by realising that it's all part of a pipeline.

\n

Flexible by having fluid categories, and having no forced values.

\n

This adds up to an attitude towards data that makes it _work for us_ . Makes it _deliver value to us_ . Not a world where we are its servants.

\n

These are just _my_ ideas. By sharing them I'm hoping that I can mix them with your ideas to turn them into really good ideas that are _our_ ideas! Comment prolifically on all the posts.

\n
\n

There are footnotes throughout. Some are me rambling in a way that would otherwise break the flow. Others are technical points that are there to add weight to the argument but are too technical for the main body of the text.

\n
\n\n[^1]: The obvious question (to Barry, I didn't think of it) is _who does feel comfortable with lots of data?_ Lots of professions need to deal with data: Psychologists, business people, statisticians, bookies, dog breeders, advertising, marketing, stock market traders... and more and more professions are being added to that list as a quantitative understanding of the world becomes a core of their business\n[^2]: this is a post, but it's still internal. I might post it one day\n", "content_html": "

A manifesto for data collection

\n

This is something I spend a lot of time thinking about. That means I’ve developed some opinions!

\n

Andrew Godwin and Matthew Blair asked me to write a bit of a manifesto that explains what I think we should be thinking about. Read the posts below in any order, but this one first.

\n

I’ll add a disclaimer too. These are my opinions, not BVN policies!

\n

Data is a huge subject. It’s also something that, traditionally, architects aren’t trained to deal with or understand[1. The obvious question (to Barry, I didn’t think of it) is who does feel comfortable with lots of data? Lots of professions need to deal with data: Psychologists, business people, statisticians, bookies, dog breeders, advertising, marketing, stock market traders… and more and more professions are being added to that list as a quantitative understanding of the world becomes a core of their business]. The main thrust of this manifesto is that we should be bold, responsible and flexible.

\n

What do I mean when I talk about data in this series? I’m talking about the things that go into the people and project pages and into timesheets. There are lots of other ways that we make data, and these are all important but I’ll deal with them later on.

\n

Bold in that we should do brave things. We should be as open as possible with our data[1. this is a post, but it’s still internal. I might post it one day]. We should set precedents by defining and controlling the API for our company and our industry.

\n

Responsible by having no admins and taking control over your own data. And by realising that it’s all part of a pipeline.

\n

Flexible by having fluid categories, and having no forced values.

\n

This adds up to an attitude towards data that makes it work for us . Makes it deliver value to us . Not a world where we are its servants.

\n

These are just my ideas. By sharing them I’m hoping that I can mix them with your ideas to turn them into really good ideas that are our ideas! Comment prolifically on all the posts.

\n
\n\n

There are footnotes throughout. Some are me rambling in a way that would otherwise break the flow. Others are technical points that are there to add weight to the argument but are too technical for the main body of the text.

\n
\n\n", "content_hash": "sha256:6072c32802313513aae660c668a9963319c9a4390e0f39308791f4d36fd44d70", "media": [], "changelog": [ { "version": 1, "at": "2015-08-23T21:01:34Z", "note": null } ], "transclusions": [] }