In the course of what I laughingly call my career I’ve written many thousands of 'work words'. Not just the day-to-day emails or in whatever this year’s favourite chat messenger is, but formal 'documents' too. Design documents, the odd bit of policy, API descriptions, integration guides, all that kind of stuff. It’s all been for internal use, not for public consumption.
Well, the world is changing in so many ways, and somehow I managed to get my name on two articles, for two different clients, published on their respective websites two days apart.
As part of our work on the ARCHANGEL project, we - The ODI - have been looking at how blockchain technology could have a place in ensuring that our public archives are trusted, unaltered, and auditable. It’s a really interesting and, given the times we live in, potentially very important question.
In truth this article was written by my colleague Jared and my input was largely advisory, but I’m grateful to him for putting my name on it too. Technical Associate! Get me!
A great deal of the work we - West Midlands Fire Service - is built on Tymly, our state machine engine. Tymly’s state machines are defined using the Amazon State Language, and as we write more and more state machines, and they’re getting increasingly complex we thought, maybe, some validation might be useful. This little blog post introduces a couple of tools, why we ported them from Amazon’s own validation tools, and how the open source nature of what we and they are doing helped us all. It’s a bit of puff piece and I should probably write about that work in a bit more detail. There’s some untapped potential in some of the code I ported, I think.
I’m lucky to be working on both these. They’re interesting things to get stuck into, the people I work with are lovely, and the results will, hopefully, make the world a better place. You don’t always get to say that.