Beware Temporal Coupling

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.