Re:Ask HN: Share your dev horror stories
by felicianotech on Tuesday October 24, 2017 @02:08PM
(#15543764)
"BirtthDate" Oh geez. That's a scary path to go down.
Yep! It then becomes a "which one is right" situation. Luckily I moved teams and don't have to deal with that anymore. I was close to quitting partly because of having to deal with that too.
Re:Ask HN: Share your dev horror stories
by quickthrower2 on Thursday October 26, 2017 @01:05PM
(#15560834)
I'd love to see the algorithm for that. It's creative to say the least. Simpler to just add 1, 2 etc to the end.
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.