Tonight I had a lot of blogs entries to post on my Software Maintenance blog. However I still had time to spell check each of my entries. One such entry took a long time to spell check. Then I made corrections and tried to post the results. I was not surprised when Blogger bombed and I lost my changes.
I was not phased so I edited the entry again, ran spell check, then successfully posted my changes. Then I went on with creating other blog posts. At the end I did a quick check on all my posts for quality control. Wouldn't you know it? The post that initially bombed still had some of the Spell Check highlighting in the actual published version. What a crock.
Luckily I was able to go back, rerun Spell Check on the blog entry, then post one more time. Now the yellow Spell Check highlighting is gone. What is the moral of this story? Double check your work, especially if Blogger acts funny when you are editing your post. I think there may be another moral lurking down somewhere inside me. However this rant is now over.
Mysterious Double Instance Hampering Performance - I study the existing code base. Confer with a colleague. Then I determine the optimal plan to change the functionality to load only a slice of all the dat...