Technology in the context of your work.

Different environments, the same failure.

An environmental program, a utility network and a fast-growing company look nothing alike from the outside. The technology problems they bring us are close to identical. Something was built for a situation that has since changed, by people who have since moved on, and the team left holding it can describe what it does without being able to change it safely.

What differs is the constraint that shapes the answer. In the field it is power, connectivity and how far someone has to drive to reach a failed device. In utilities it is the obligation to show what happened and when. In a scaling organisation it is that the system was built for five people and is now carrying fifty. The same discipline applies in all three: understand the work before changing the system, and hand back something the team can operate without us.

We work across all three because the patterns transfer. A normalisation layer built for flood telemetry is the same idea as the integration layer between a lab system and a billing system. Seeing it in one context makes us faster in the next.