lewiscowper/gist:bbb8e51fda00ff080058

## gistfile1.txt
Are there any ways of getting to a Dreamcode API with little or no knowledge of how APIs work? I'm interested in API design, and I was wondering how you make the collabarative decisions on how the Hoodie API works, hopefully I can make a blog post about the ideas behind it.

I see the DreamCode/API-first design process as a really nice way of making sure your backend devs and front end devs are working in sync, toward the same goal, because the example request and response are there from an early point, allowing both to work and (hopefully) allowing the two to glue together quite well.

Basically my overall question is, how do I determine if an API is good/better/best from a design point of view, without implementing it.
	Are there any ways of getting to a Dreamcode API with little or no knowledge of how APIs work? I'm interested in API design, and I was wondering how you make the collabarative decisions on how the Hoodie API works, hopefully I can make a blog post about the ideas behind it.

	I see the DreamCode/API-first design process as a really nice way of making sure your backend devs and front end devs are working in sync, toward the same goal, because the example request and response are there from an early point, allowing both to work and (hopefully) allowing the two to glue together quite well.

	Basically my overall question is, how do I determine if an API is good/better/best from a design point of view, without implementing it.