Mocking API's in Golang... for fun AND profit!

Software development in 2016 is a crazy complex process. Modern applications are increasingly distributed, regularly requiring access to an array of systems controlled by 3rd, 4th and 5th parties. So what happens when we are building the next killer-app-uber-disrupting-unicorn and the API that we NEED to access goes down?

Slam our Macbooks shut, whine about up-time and go home?
Consume our body weight in caffeine in preparation for the glorious return of the API?
Sit quietly and wait for morning to come?

Why Drupal 8 won't ship with REST content negotiation

Some friends on Twitter were alarmed by this Drupal change record: "Accept header based routing got replaced by a query parameter". This change replaces "Accept: application/hal_json" with "/node/1?_format=hal_json". The issues leading to this change are too lengthy to capture on Twitter, so I'll give my perspective here.

Simple password grants with OAuth 2.0 and Drupal Dylan Tack Wed, 09/10/2014 - 08:30

Like many Drupal developers, we have become big fans of decoupled front-ends using Drupal as a RESTful backend (a.k.a. "headless" Drupal). The myriad of authorization options can be confusing, however. We've settled on OAuth 2.0 for most situations. When OAuth is brought up, many people will think of the single-sign-on flow in a browser, with the associated redirects and permission dialogs. This flow is widely used, but not always a good fit for first-party applications, or machine-to-machine API interactions.

Ready for transformation?