First dev job after 2 years of working non-tech and doing data entry. It was a debt collection agency (took whatever dev job I could get) that specialized in st

First dev job after 2 years of working non-tech and doing data entry. It was a debt collection agency (took whatever dev job I could get) that specialized in student loans. Well, it turns out they were doing interest calculations in SQL Server. Funny thing, well not so funny, is that the output was generating interest that was incorrect. I sketched out the numbers and did the math on pen and paper and found the interest should be and what they were calculating were different. I fixed the bug and things were fine after that. The other horror story was at my current job. There was a data transformation that needed to happen to take data from one system and put it in another. Both databases happened to be on the same server so the person who designed this decided to use several SQL stored procedures to accomplish this task. This is where the fun began. First, if there was already a column named something, such as "BirthDate" and this individual wanted to use a column with the same name, instead of re-using the column that already exists and populating it with the correct data, he would create a column named "BirtthDate". Now that example is made up, but he would frequently purposely misspell words to make unique column names to avoid conflicts with columns in the same table that had the same name. He also would do calculations in his stored proc but then would never use the result, or he would set the variable holding the result to a static value lower in the SQL stored proc. It made things very interesting.