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.
19 Dec 2017
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.
07 Sep 2017
I originally wrote this as talking points for a conversation I had with my team and wasn’t planning on sharing it more broadly. However, as I’ve been watching this crazy industry of ours over the last several months, I think that these thoughts apply to many more people than just those on my team and I hope that at least one other person finds them useful.
16 May 2017
“A rose by any other name would smell as sweet”
04 May 2017
Over the last two years, I’ve had the opportunity to look at a number of different API Gateway products as well as participate in the design and development of a fit for purpose gateway service for my company. Through these opportunities, I have landed on a conclusion about the current API Gateway landscape and a vision for the future of API Gateways.