Interesting approach. In general, I always prefer 'Infrastructure as files' as the article calls it. I think if that's not possible in any specific scenario then we just didn't create the right abstractions yet. In the devops space I think we're still a far way off, so tools like the one mentioned in the article can help us get there. But I would not think they should be the ' user interface', so to say. That should be a data structure of some sort, ideally as small as possible, typed and validatable.