Agile methodologies often excuse poor planning, but nothing ever goes to plan anyway. Is there a better way?

“Good companies excel in creative use of slack. And bad ones only obsess about removing it.”

Often, as technically-minded folk, we have an urge to fix things for others. I call this the "see a problem - solve a problem" trap.

Meet Obsidian, the best note-taking tool I've found in 25 years of looking.

Hardware is hard. And that’s despite the fact that teenagers now regularly toy around with technologies that electronics engineers would have struggled with 10 years ago. The problem is not the lack of resources, but that the hardware development process has stagnated. Brilliant engineers run at the speed of

Visualising COVID-19 data, aka, what the heck is a Choropleth?

I started programming when I was old enough to reach the keyboard. Typing BASIC listings out of the backs of computer magazines into the family Apple IIe so I could play games before the Internet or even hard drives were a thing. And then realising I could modify the game

More than a decade ago, when I needed a pithy modus operandi statement for this new fangled LinkedIn thing, I came up with this: > Successful innovation comes from adeptly alternating between the thousand foot view to ensure the intent is being met, and the microscopic view to ensure the technical