mxplx

Beware Temporal Coupling

Published by ideonexus

When people first sit down to design and architecture or write a program, things tend to be linear. That's the way most people think--do this and then always do that. But thinking this way leads to temporal coupling: coupling in time. Method A must always be called before method B; only one report can be run at a time; you must wait for the screen to redraw before the button click is received. Tick must happen before tock.

Andrew Hunt, David Thomas, The Pragmatic Programmer: From Journeyman to Master (Oct 1999)

Notes

Coupling things in time is a natural result of the linear design of a system.

References

Schemas

Not in any schema.

Triples

Not related to other memes yet.

Watson’s reading

Tags generated by IBM Watson from the text. Percentages are its confidence.