Backwards compatibility is one of the most crucial factors of when and how to release a new feature. Maintaining a stable API while constantly improving your service is critical - you don’t want to be breaking your API clients every second Tuesday. In this simple example I want to share how fields that are enums (commonly status fields) are crucial parts of your API stability and how changing them is a terrible idea.
Surprise (or no surprise) - I’m in Seattle for #MSBuild this week! I’m also delighted to be part of a small Microsoft-invited group called TAG (Technical Advisory Group), composed of folks from around the world with a strong open source tech background.
Our itineraries are packed, and I’ll be sharing some of the sights, insights and delights along the way.
In today’s itinerary, we’ve been treated to a round of shiny toys and tech-theatre.
Ever found yourself finding nothing to contribute to a meeting? Or perhaps giving one piece of somewhat token input as a stakeholder and otherwise uninvolved? Yeah I get that a lot. Meetings sap hours of my productive time everyday and leave me wondering where my day went. I call it being meet-napped!
I’ve slowly established some fairly stringent techniques to ensure that my time is used most effectively and to not waste others’ time in meetings either.
A little over 3 months ago I started doing a thing, every day, for 100days. No one knew what it was, when it was done or why I was doing it. Earlier this week, I finished & achieved that challenge; and here’s why!
It’s become somewhat of a tradition to do a PHP version round up at the end of the year. In 2014 Anthony Ferrara posted PHP versions in the wild and last year I continued the tradition (with his blessings) with my PHP version roundup post. This is a continuation of that post.
In this post I’ll be detailng:
patch version fragmentation % change in install numbers % of installations running an insecure or out of date PHP version.