Deployment / Delivery Frequency

I often end up needing to advocate for more frequent delivery/deployments with clients.

There’s the usual benefits commonly discussed such as improved feedback, reduced risk, well understood processes, maintainable dependencies etc… however what’s often missed entirely is how it relates to the health and sustainability of the team.

Github Actions is a “BYOBE” (Bring Your Own Bloody Everything) offering that provides basic CI with surprisingly convoluted configuration to Github.

The product as a whole is an exercise in frustration, one of the worst parts is the lack of reusability and the complexity required to achieve it. Github’s concept of reusable workflows on Github Actions is clearly a cobbled together afterthought.

The YAML Spec defined a simple way to reuse values in YAML documents by means of Anchors and Aliases .

As of 2022, I’ve been using zsh as my primary shell for 14 years.

Over that time I’ve experimented with and accumulated a lot of configuration, scripts, hacks, plugins and themes. I’ve settled on a configuration that I’m mostly happy with, over this series I’m going to share my current setup.

Contributing to Open Source is important to the quality and maintainability of the software and engineering communities we rely on every day - so why is it that so many developers/engineers never participate?

We create more value by having conversations in public instead of behind closed doors.

Near the end of each year I note down a summary of the best apps I’ve enjoyed using throughout the year, here’s 2022.

We’re (still) not deploying enough

It’s 2022 and not deploying frequently enough is still one of the most common causes of software failure.