Software development notes.

How to specify behavior, examine an API, move data and hand software over to its next maintainer.

Planning a spreadsheet migration

Work through a sample import: trace the source rows, define their rules and account for accepted and rejected records.

Check whether the API can carry out the required operations, at the required volume, using access the business can maintain.

A requirement is easier to review when it names the starting data, the action and the result someone should observe.

The next maintainer needs to build the software, understand its dependencies and recover it when an operation fails.

Giving other people access to a script raises questions about permissions, run status and what happens after the browser closes.

Compare repairs and replacement against the behavior the business needs to keep, including its data and external connections.