A tool or a colleague

Most software waits to be used. The useful kind pays attention even when nobody asked.

Waiting and watching

A tool waits. It sits idle until a command arrives, does exactly that, and goes back to waiting. That is a fine way for software to work, and almost every program architects use today works this way.

A colleague watches. Not by interrupting, but by noticing in passing that a detail on sheet A-401 no longer matches the one on A-402, without anyone asking them to compare the two.

Why the difference grows with the project

On a small job, one person holds the whole model in their head, and the difference barely matters. On a larger one, with more disciplines, more sheets and months of decisions, it becomes most of the job.

A system that watches a live model and flags an inconsistency nobody asked about is doing something different in kind, however good the drawing tools are.

What paying attention needs

Three things a request-and-response tool does not have: context that persists, initiative within limits, and restraint. The third is the hard one. A system that flags everything is as useless as one that flags nothing.

Where this leads

None of this means tools are bad. Plenty of software should stay precise and on demand. But the parts of a design workflow that involve ongoing checking are the parts that benefit from something closer to a colleague.