Embarrassing Programming Mistakes
Everyone knows that I have been and continue to be an active software developer. After I wrote my last blog post, my ex-boss at Wesleyan (John Meerts) reminded me of the first homegrown registration system that I helped write at Wesleyan in the mid 1990’s. This was a game changer at that point and it created the trust of the community in our abilities. This allowed me to both write and lead several other major programming initiatives there which I have carried with me to other institutions.
But, as a software developer in small institutions with small staff to work with, you always encounter issues. There is a lot of excitement around software development, but there is also a lot of risk involved. The community comes to rely on them and wants constant enhancements which can never be predicted ahead of time. Also, with constant changes to the web browser and underlying technologies, you need to continually monitor and apply fixes. As a result, we end up struggling to support these in the long run. Also, when we write our own, our capacity to thoroughly test them is limited and it leads to mistakes. I just wanted to highlight some such mistakes that I have committed myself or have seen it done by others. For the sake of anonymity, I am not going to say who committed which one and leave it to your imagination…