User input and output Code Diary Entries

This is part of the Semicolon&Sons Code Diary - consisting of lessons learned on the job.

• Always strip whitespace when searching exact match user input
• Ask about expected date time formats before writing code
• Assume unformatted floats need rounding
• Clis should not use dollar signs for argument specification
• Consider whether two filters combine as 'and' or 'or'
• CSV file issues
• Hold back on string validations until very sure of data format
• Mission critical software should communicate internet connectivity with users
• Preface error messages with the word error to disambiguate from logs
• Reset password errors must give time period
• Test against bogus or impossible user input
• Whenever splitting on delimiter prepare for white space or nil entries