> Why should the dev be making these quiet decisions, is this not evidence of incomplete requirements? If the requirements were a complete specification of wha

> Why should the dev be making these quiet decisions, is this not evidence of incomplete requirements? If the requirements were a complete specification of what the program must do in every circumstance, you could directly compile them to create a working program. Requirements documents are not intended to specify everything—only enough that a competent person would get the important things right. Filling in the trivial details with reasonable behaviour is basically the programmer's job.