The last responsible moment mindset can at times lull me (erroneously) into thinking that I’ll always have time to change my mind if I need to. I’m ever the optimist. Yet in order to work well with others and to produce habitable software I sometimes need a little more forethought. And so, I think I operate more effectively if I make decisions at the “most responsible moment” instead of the “last responsible moment”. I’m not a good enough of a designer (or maybe I am too much of an optimist) to know when the last responsible moment is. Just having a last-responsible moment mindset leaves me open to making late decisions. I’m sure this is not what Mary and Tom intended at all.

decisions that initially appear to be localized (and not to impact others who are working in other areas) can and frequently do have ripple affects outside their initially perceived sphere of influence

I am not known as someone who plans things far out in advance. As a consequence I rarely use frequent flyer miles because I don’t anticipate vacation plans far enough in advance.

Deciding too late is dangerous, but deciding too early in the rapidly changing world of software development is arguably even more dangerous. Let the principle of Last Responsible Moment be your guide

delay commitment until the last responsible moment, that is, the moment at which failing to make a decision eliminates an important alternative

developmental delay

developmental delay

Monitoring Latency (How Low Can You Go?)

Today, most delay units are digital, but they often include controls to help them emulate the characteristics of the early tape units, including distortion and low-pass filtering in the delay path and pitch modulation to emulate the wow and flutter of a well-used tape transport.

the median review time at journals has grown from 85 days to >150 days during the past decade (5)