Recently I “resolved” a bug. About one week later, my co-worker alerted me to an issue with my fix. The issue had to do with a t-sql statement that used an id in its where clause. I forgot to put this id in single quotes.
MS SQL Server assumed that I intended for this value to be an integer due to its lack of single quotes. As a bonus, it never generated a parsing error.
However some customers configure their id format to be larger than an integer ( > 10 digits). This experience taught me the importance of testing with dirty, bad or troublesome data. Troublesome data saves you by exposing issues early, while “comfortable” data obscures them.