Going "what if?" and then validating a customer requirement that exists NOW is N...

zephen · 2026-03-19T01:27:51 1773883671

> Audit trails are commonly neglected coz somebody didnt ask the right questions, not coz somebody didnt try to anticipate the future.

But how do you ask "the right questions" without imagining many future possibilities and then trying to discern which ones are important?

It seems like a distinction without a difference to me.

rglynn · 2026-03-19T16:46:55 1773938815

Imagining future possibilities and implementing software to account for them are two different things.

The argument here is to validate those possibilities before acting on them.

zephen · 2026-03-19T17:06:37 1773939997

> Imagining future possibilities and implementing software to account for them are two different things.

True.

> The argument here is to validate those possibilities before acting on them.

I agree this should be done. It's not clear that was the original argument, because the same guy previously wrote:

> The number 1 issue Ive experienced with poor programmers is a belief that theyre special snowflakes who can anticipate the future.

"The future" is a not-so-special case of "the now."