In “A Foolish Consistency,” the author briefly describes the importance of consistency in technical writing. The post referred to a time where the author noticed a missing period in the user interface of an error message. When he alerted the Development Team of the error, they responded that they were merely being consistent with previous messages that also did not have periods. The author decided that they would begin to use periods on the new error messages, because there is no point in being consistent purely for the reason of being consistent. If changes need to be made, make them.