• 29 Nov 2017

    I Don't Work for a Technology Company

    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

    On Change and Career

    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.

  • 04 May 2017

    Thoughts on a Next Generation API Gateway

    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.

  • 12 Mar 2017

    My Workflow

    I initially became interested in personal workflow methods and tools when I started at Microsoft in 2006. Microsoft differed from my previous roles in that projects generally required coordination across multiple teams - meaning that there were lots of tasks to manage. Additionally, the corporate culture made heavy use of emails and meetings - meaning that tasks could originate from a variety of sources at almost any time. Without some kind of structure, working at Microsoft could very easily become purely reactionary. And as you may have experienced in your own work, reactionary work may keep you busy, but it doesn’t make you very effective. Most importantly, this kind of work doesn’t feel very satisfying.