Software updates are as innevitable as death and taxes, yet smart-contracts are designed to be immutable. This article takes a look at how we can reconsile these two world views for the Tezos system.

I've recently been tasked with maintenance of 4C's Tezos smart contracts: taking them from research project proof-of-concept to something ready to deploy. Here's my notes on how to work with Tezos as a software engineer.

Taking the batch processing I was doing with geospatial data in the last post and instead doing the same visualisation in real time on the GPU using shaders.

A look at how large geospatial datasets are stored and processed, some tips to quickly see what's in the files, and how to get such data onto an interactive webpage map.

A look at one of my new projects, putting my engineering skills towards a project tacking the ongoing climate crisis with a team at the University of Cambridge looking at verifiable carbon offsetting.