Notes on building software that has to work.
Written for buyers and technical leads. Each one is something we apply on our own projects, set down so you can use it on yours.
Data migration: reconcile before you switch
A migration is finished when both systems agree and someone has signed to say so, not when the script exits. This is how to plan one so that the night of the switch is dull.
How to write a specification a supplier can quote against
A supplier can only fix a price for work that is written down. This guide covers what to put in the document, what to leave out and how to handle what you do not know yet.
The quiet ways an integration fails
The expensive integration failures raise no error. Both systems report success and the data is wrong. Here are eight of them, how each one surfaces weeks later and the check that catches it on the day.
What an audit trail has to record
An audit trail answers six questions about every change to a regulated record: who, what, when, from what to what, from where and why. If one is missing, the log cannot settle an argument.
If one of these describes your problem, write to us. We reply within 2 working days.
Start a project