Yes and no. What I'm reading [1] is that they're advocating for side-by-side decoupling. In other words, humans and computers need different interfaces. Rathe

Yes and no. What I'm reading [1] is that they're advocating for side-by-side decoupling. In other words, humans and computers need different interfaces. Rather than try and build one, which is bad for both [2] build 2, one for the humans (however you prefer) and one for the computers (REST API). Perhaps I'm reading it this way because I'm prejudiced, (I've written our systems this way) and it seems to be working well. [1] this whole article is both well formatted, and seems to make a good post, but equally seems to feel like you're not sure what it's trying to say. Perhaps it makes more sense in context,rather than as a stand-alone article. [2] the computer-client team has different needs to the human-client team. One wants a very stable API, the other wants regular changes. One is content driven, the other process driven. Ultimately they want different things making two interfaces makes both teams happier with less conflict between them that you have to umpire.