Dariusz is not downplaying the value of strong code, testing, and architecture practices.

The point is that software/data solution development is not an art form but an engineering discipline. Not understanding this can turn some of the smartest people on the team into some of the lowest value contributors. The value can even be negative if the adherence to artistic principles of software/data get in the way of delivering business value.

I had to learn this myself early in my career, and I can remember freelance projects I worked on where I blocked business value over zealous pursuit of stylistic and artistic elements of software development.

Striking the right balance is not easy. Agile is supposed to help us do this, in theory, but in practice does not help much (because in practice nobody really does agile).