developer_experience

Building a DevX Maturity Matrix I promised in Part I of this article that I'd explain how I generate the headline numbers that I report as part of the KPIs or OKRs for the Developer eXperience of a product. The answer is rather simple but, at least initially, quite labourious. Reminder: what a maturity matrix is. A maturity matrix encodes a maturity level as a value (typically a positive integer) for every unique combination of product, feature, customer/developer type, and maturity type....

DevX is not just about what we create For all the good that a Developer eXperience team can do, by creating documentation, improving APIs, building tools and libraries, and fostering community, this will only ever constitute part of the total developer experience. The foundation stones of a good developer experience are actually in the hands of the core product teams. Delivering a quality product, which does what it should, and does it reliably, is the bedrock on which any developer's eXperience is based....

Introduction This blog post will introduce the Maturity Matrix I have been developing to help report on the state of Developer eXperience for a given product. In this first part, I'll explain why I think it's needed, what I report from it, and what those reports mean. In Part II I'll explain how I produce these numbers. KPIs and OKRs for DevX are hard Knowing how to describe goals and measure performance against those goals is a challenge for every DevX team....

The history of my blog If you look back through my historic posts (many of which I’ve recently migrated here from my historic blog spot blog), you’ll notice that I’ve been blogging, on and off, since 2007. That’s actually not true - I had done some previous blogging on another platform (all now lost), and actually I’d written occasional thoughts on various “home pages” going all the way back to 1995....

Software Engineers don’t scale … or how I learned to stop worrying and love commenting my code. NOTE: I originally published this on the Inside Heetch blog This article, by Mathew Skelton and Manuel Pais, reminds me that, for everything that’s been made simpler in this era of cloud computing and micro-services, we’ve paid a price in terms of cognitive load. We simply need to keep more context in mind when making or evaluating any change to our code....

Those of you who know me may be aware that at the end of August 2018, I left my job at Avocet to join a new team at Heetch. The main allure of the role at Heetch was the chance to be part of a team deliberately set up to act as a catalyst for product developers. The concept under which we work is known as “Developer Care”, and back in November I wrote a fairly extensive blog post for Heetch about what that means and how it came to be....

A useful dialog There is an application that I have been working as an employee and a consultant for five years now. In the course of development I routinely run into a dialog in this application that handles errors at a global (or at least global to the GUI) level. This dialog is very useful, it stops the GUI bombing out totally and presents the user with the sad news that something has gone wrong and allows them to report such an error....