- Run the new beside the oldA change runs beside what it replaces until it has proved itself. When the platform moved to Google Cloud in 2020, the database was replicated to a new database beside the old one.TermoSense, 2020
- A few first, then the fleetSince 2014 Joakim has tested locally first and rolled out step by step. About 25 gateway releases from June to September 2026 went first to a preview group and one test gateway in the field, then to the rest of the fleet.TermoSense, 2014 and 2026
- Alarm when it goes quietFrom July 2009 the platform sent an SMS when a gateway stopped answering. In 2026 Joakim added alerts that fire when a regular check-in stops, and the new gateways stay reachable for recovery when they go quiet.TermoSense, 2009 and 2026
Where Joakim has done it
- Replaced the laptop wired to the sensor receiver at each installation with a small Linux gateway I built, and ran it beside the old set-up as a live trial before the switch.TermoSense, 2009
- When SensiNet brought out hardware with several sensors per device in 2011, reworked the data model into one sender carrying many sensors, and moved the existing data, about 23 million reports, over while reporting carried on.TermoSense, 2011
- About 25 gateway releases from June to September 2026, staged through a preview channel and a canary box before the rest of the fleet.TermoSense, 2026
- Rebuilt the database replica and the nightly backups, and added alerts that fire when a heartbeat stops.TermoSense, 2026
- Once people other than me could change data, I added history tables filled by database triggers: changes record who made them, and a record can be rebuilt as it stood at any time since.TermoSense