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.