One of the most commonly-implored techniques that I’ve heard by the REST faithful to shut down any questioning of the faith is what I’ll call an “appeal to the WWW”. There are variations, but they all tend to sound something like the following (I’ve added the snarky rhetorical phrasing because that’s what all variations sound like in my head):
26 Jun 2018
02 Apr 2018
I received the following question from one of our service teams last week and thought it was likely the type of issue that a lot of you are dealing with (or have solved) in our current world of “microservice all the thingz!” The question went something like this:
14 Mar 2018
Every now and then, somebody will ask me what I’m currently reading or researching. As such, I want to provide my current reading list along with the top items on my backlog. I’ll also try to publish these posts more frequently so that you [and I] can track progress as well as see what topics and resources have sneaked in.
19 Dec 2017
Some of you may know that I’m passionate about helping people from non-traditional computer science background enter our industry and have done quite a bit of work over the last few years towards that end through partnerships with immersive code schools like General Assembly and Code Fellows. In fact, at this point, nearly one third of my organization has come from one of those programs.
29 Nov 2017
One of the projects that my team works on is a GraphQL server. The service provides a consistent, data-focused interface between multiple types and versions of front end applications and multiple types and versions of back end APIs. Now, let me be clear up front: this post is not about GraphQL vs. REST. As I’m sure will be unsurprising to the vast majority of you, our back end services differ wildly in terms of design (from RPC to “Pragmatic REST” (aka RPC) to full-blown hypermedia), content types and granularity of resources. So our decision to use GraphQL is based on what I think are 3 realities that are specific to a company and a culture.