Phil Sturgeon

Sign in Subscribe

Phil Sturgeon

Phil Sturgeon

Software Engineer gone ferril. Digital nomad since 2018 (bike/van). Now dedicated to woodland creation and restoration, as co-founder of UK climate chairty Protect Earth.

DCCX 2018

DCCX 2018

DCCX was a road-trip weekend down to a UCI race around Lincoln’s summer home… or something. Two very different days, with two very different results! A DNF Saturday and a 4th/120 on Sunday! 🤘🏼 This weekend taught me a few things, mostly that races are won or lost before

Catching Up on Cross Season 2018

Catching Up on Cross Season 2018

Some of the big takeaways from last year were about breathing. My last race Elm City was a mess once my nose turbine (a little plastic doohickey that helps me breathe) fell out. Sick of putting it off, and tired of spending $40 for three little things that I can

Poutine or Bust: NYC to Montreal

Poutine or Bust: NYC to Montreal

Nobody wants to hear about sweating away on TrainerRoad so I’ve been quiet since cross season was done, but now I have an adventure to write up: cycling to Montreal, 1x 100mi, followed by 1x 200mi! A lot of people were confused about why on earth this was my

Picking the right API Paradigm

A while back I wrote an article called Understanding RPC, REST and GraphQL which outlined the "what" in how these various approaches differ. This got a few people thinking I was saying REST was drastically superior in all ways, which is a common conclusion when folks hear me

API Evolution for REST/HTTP APIs

API Evolution for REST/HTTP APIs

There are a lot of pros and cons to various approaches to API versioning, but that has been covered in depth before: API Versioning Has No "Right" Way. API evolution is making a comeback these days with GraphQL and gRPC advocates shouting about it. Whatever API paradigm or

Design-first API Specification Workflow Matures

Back in October I wrote Chasing the Perfect API Specification Workflow, which was a huge article about the state of the API specification world. One person trying to figure out a good workflow, in a sea of alternative specifications, with incomplete tooling, making it hard to see a solution for

Still Going on REST is the new SOAP

Still Going on REST is the new SOAP

One month after A Response to REST is the new SOAP and I'm still having a productive dialog with the author, helping him understand how REST works. I thought it might interest some of you too. Pakal de Bonchamp Thanks for the lengthy article - we unexpectedly agree