The Biggest Mistake! A Programmers' Nightmare!

Tweet

Just moments ago, I debugged the big big mistake I did while doing some patch work in an ongoing project. The database was denying to accept any more record! I tried every possible way but could not resolve the issue. The script involves lots of fine tuning and third-party components. So, you can guess my situation. I was absolutely clueless, horrified, and ended up the issue unresolved last night! It was like a nightmare. It is said we need to debug logically based on knowledge and experience. Yet at times I get tempted. I just can't stop experimenting to locate the source of the problem. However, this time finally the issue was resolved all of a sudden when I discovered to my surprise - my entry was creating a duplicate key in the database, preventing further record insertion. Oops! Too simple! But our product website suppresses all routine debugging information - so, you can imagine - it's almost like walking down a dark lane full of strange and invisible creatures. Thankfully, it was resolved. And I am now feeling better and keeping my fingers crossed. Hopefully, the next time if any problem appears, I'll start checking for the duplicate index issue right away! This was my story! Now to give some sort of courage and relief to me, can you share - what's your biggest mistake as a programmer? How did you resolve this? Is it still your nightmare or an unresolved mystery? Please share your thoughts.