I really like Read the Docs - a great documentation hosting platform, free for open source and community projects.

I really like Pipenv for managing my Python project dependencies.

Unfortunately Read the Docs have decided to not support Pipenv. This is perfectly reasonable of them - it’s their service, and everything they decide to support incurs a cost. Alas it’s not quite ideal for me!

Fortunately both tools provide useful compatibility features that make it pretty straightforward to get them working together:

Update (2025-04-19): Netlify CMS is now Decap CMS

“Netlify CMS is an open source content management system for your Git workflow that enables you to provide editors with a friendly UI and intuitive workflows”. Note that it’s entirely orthogonal to the Netlify hosting platform - using one doesn’t commit you to the other, but there’s definitely some convenience factor from using both together.

I just added it to this blog and I really like it!

Dr. Aaron E. Carroll writes in The New York Times:

Denise Yu’s great thread covers a fundamental yet often overlooked ability, and provides practical ways to deploy it:

I joined Twitter back in 2010 and have loved it. Like so many of these things, I find you get from it what you put in, and over the years I put in lots of effort curating my timeline so that I followed a fantastic selection of people and groups that brought me knowledge and joy.

I am a licensed radio amateur. Wikipedia describes Amateur Radio as:

Amateur radio, also known as ham radio, is the use of radio frequency spectrum for purposes of non-commercial exchange of messages, wireless experimentation, self-training, private recreation, radiosport, contesting, and emergency communication. The term “amateur” is used to specify “a duly authorised person interested in radioelectric practice with a purely personal aim and without pecuniary interest;”

There’s an incredible range to the hobby: some like to simply talk to others nearby, some like to see how many different places they can communicate with, some enjoy travelling to different islands or mountains to contact others, some are interested in electronics and building radios, and some like to communicate by bouncing signals off the moon.

I’m less interested in the human communication aspect, and more in the technical, particularly in exploring the “hidden” world of signals around us all. Actually, given I do very little transmission and instead focus primarily on what I can receive, I make relatively poor use of the permissions my license grants me!

ESPHome is a remarkably simple yet powerful framework and toolchain for programming ESP8266/ESP32 boards. ESPHome provides a whole bunch of “components” - pre-built modules to manage the underlying hardware/functionality - and lets you enable, configure, and integrate them with a few short lines of YAML.

ESP32 (and the ESP8266 predecessor) is “a series of low-cost, low-power system on a chip microcontrollers with integrated Wi-Fi and dual-mode Bluetooth” with a wide range of uses, but particularly valuable for IoT and/or home automation.

There are relatively inexpensive dev boards (£14 on The Pi Hut), and a whole bunch of commercial “smart” devices built on top of an ESP core.

There are many ways you could write a job advert, but, absent something pre-existing to work from, here’s the skeleton template I use.

This was written as part of wider documentation about ensuring healthy and inclusive hiring practices, so isn’t a self-contained fully-fleshed-out thesis, but it’s been handy for me to use and re-use.

The examples are a little contrived and brief, but should serve as a basic indicator of the kind of content intended.

I have a number of Software Defined Radios (SDRs), ranging from cheap RTL-SDR dongles originally designed to receive TV, to the much fancier Hermes Lite 2 transceiver.

OpenWebRX is powerful yet easy-to-use remote SDR receiving software, that you can operate from a browser. It’s designed for people to offer radios to a wider audience over the internet. For me, it’s valuable on my local network.

I’m a big believer in the value of “real” DevOps - culture, collaboration, breakdown of silos, etc.

But the lack of a formal definition has often made it feel challenging to explain, particularly as it’s so widely and often superficially used - “our ops team is now the devops team” etc.

I’ve finally found an introduction and explanation I want to share: