We'll respond shortly.
In this post, Pivotal Labs Engineering Manager, David Julia, provides an example of a problematic RESTful JSON API and an approach for refactoring it. When API designs are implicit, they don’t reveal and enable the intended API usage, and they become very difficult to implement. In today’s world of cloud connectivity and developer community, poorly designed API can greatly slow down or stop software service adoption in its tracks, not to mention the public feedback for poor APIs. David’s approach, and the related code, clearly explain some of the key considerations.
I’ve been undergoing a "Test-Driven Development (TDD) Midlife Crisis", in which I've been critically examining how I test drive code. During this process, I've been thinking about the kinds of tests I write, how much I mock, when to mock, and other fundamental questions of test-driven development. Over my Thanksgiving vacation, I re-read the seminal book on TDD, Test-Driven Development By Example by Kent Beck. It's a quick enough read, which reminded me of something that I'd been saying for a while without fully understanding the implications: TDD is more about confidence in your code and designs than it is about proving correctness. Here’s how I went about re-familiarizing myself with this concept.