How we think about building trustworthy systems

People bring us work that matters to them, and that sets a high bar. A trustworthy system is one whose behaviour can be predicted, inspected and corrected.

In practice this means preferring explicit steps over hidden automation, keeping a durable record of what happened, and making it obvious when the software is uncertain.

These principles are not abstract. They decide what we build, and just as often what we choose to leave out.