I'm still digesting the full article, great different angle to look at things. My comment hence is purely focussed on the reply of mr_toad. For me, the core of

I'm still digesting the full article, great different angle to look at things. My comment hence is purely focussed on the reply of mr_toad. For me, the core of the mesh idea is the fact that everything is a people and cultural problem, that's the core of the paradigm. I do agree however, that too much content on the topic addresses the technological implications of it. It's (only) the means to an end. And this people and cultural problem, needs to be fixed both bottom as up. Yes, you need to find developers who care about the data, but you also need management to not slap them right back. In fact, it should be managers to tell developers that it is their job to offer the data back to the organization in a reusable format. That's when you have reached a true data literate and data driven company. What the mesh idea tries to resolve, is that a central data team can not understand all domains and business goals and data linked to it. Rather than pursuing this dream, it aims to explain to the domains, and in your example developers and admins, the value of data in general, which just might have a bigger chance of success.