[avastmick]

My take is that it is attempting a similar “intervention” as the Agile Manifesto did, but less well thought through or phrased.

The data science/ engineering domain appears to often produce outcomes like a good deal of 1990s software projects - projects that don’t produce good or expected results [0].

I posted a counterpoint recently [1] that said we should stop approaching data engineering like software engineering. Given what appears to be an almost endless number of data projects that produce little to no value to businesses, what should data professionals do to address the problem? This manifesto at least attempts to make a statement.

[0] I contributed to many of these at the beginning of my career!

[1] https://betterprogramming.pub/data-engineering-is-not-softwa...

[jerglingu]

In your article, your points about managing stateful data operations vs stateless tools is right on point. It's the eternal and ever-repeating argument that has to be made in every data shop I've ever been in when inevitably a manager or senior person suggests moving to scrum, because of this propagated lie that data engineers are just like software engineers. Glad to see it in writing.

[civilized]

Data engineering isn't software engineering, but it needs better software tools big time.