I’ve been having a bunch of conversations with my team about our career ladder, and what it means to be “senior” in a software engineering context. It’s a little different in every company, but here is my view.

Anecdotally, one of the more maligned features of the Heroku platform are the 24-hour limits on compute units, known as “dynos”. This is actually a good thing, but very misunderstood.

A quick explanation of the Okta AD/LDAP DelAuth bug that was being shared around, and the importance of sensible defaults.

There are two programming principles that I hold dear to my heart: the principle of least surprise and provide sensible defaults. I’ve recently been working within the GraphQL ecosystem, and the number of violations of both here has frustrated me. This will be a little bit ranty.

I’ve been managing a fully remote, fully distributed team, covering timezones from UTC-8 through UTC+10, for the last couple of years. Through that time, I’ve learned a lot on organising work, interpersonal relationships, and ultimately how to overcome a lack of promximity to my reports.