I caught sight of a Github action which publishes and tags Ruby gems. It (hopefully) makes upgrading a little easier/more efficient. It’s one less thing maintainers need to worry about when managing a ruby gem.

We had a talent acquisition and retention problem. Here’s how we solved it:

The following is a summary of “Secrets of Consulting” by Gerald Weinberg - here is the LeanPub link or you can purchase it on Amazon, interspersed with my own thoughts and experiences. This post details the genesis of that purchase.

I had a crack at consulting yesterday. As I was randomly cruising Air Tasker - admittedly not the best place - I saw a posting I had expertise in: AWS Costing. Perhaps it would be a fun little job for me. I wouldn’t mind the occassional consulting here and there. But the problem is that you have to deal with people.

I’ve been using Elm in production for 1-2 years now. Love it. Advantages?

This is an attempt to explain AWS IAM principles.

What is the problem?

Warning: this article uses terms of art that may not be comprehensible to the lay man. I depart from my policy of explaining everything simply, because I’m using this as a reference for myself, and don’t want to belabour the task with tedious analogies - so I beg the reader’s patience.