Explicit is always better than implicit
After a week working like bureaucrat Conrad I buckled down toward the end of the week to check things off the list. I got to a couple of problems that seem to show up in most organizations. If you want good programs it is always helpful to remove ambiguity in your requests.
In many organizations it is easy to leave out the details and let someone else sort it out. Ever wonder why you have to hit the # after entering your zip-code on the phone? I wager someone at that organization refused to make a decision and the programmer who couldn't pass the buck figured out a way out of the jam. "...We need a way to say 'End of Input'..." You as a user find it daft, but remember this next time you refuse to think a project through. Computers are unforgiving that way.
This sort of decision made their life easier rather than having your program crash.
In many organizations it is easy to leave out the details and let someone else sort it out. Ever wonder why you have to hit the # after entering your zip-code on the phone? I wager someone at that organization refused to make a decision and the programmer who couldn't pass the buck figured out a way out of the jam. "...We need a way to say 'End of Input'..." You as a user find it daft, but remember this next time you refuse to think a project through. Computers are unforgiving that way.
This sort of decision made their life easier rather than having your program crash.