Just when you think you are out of the water, the shark known as Blogger comes up to bite you. Today I submitted a post to my IBM Tools blog on Client/Server and DB Objects. Prior to publishing this large post, I saved the text to a Notepad file. The post published fine. So I assumed all was well with Blogger.
Then I tried to follow this post up with another one about DB2 storage, SQL, and security. I did not bother to backup the text prior to publishing. Big mistake. Blogger choked and gave me an error message. My text was lost. This is all too familiar of a horrific experience. Can't Blogger remain stable for even one day? What kind of buggy system are they running over there at Google?
I might have to start copying and pasting the text each time before I submit a post. Because I don't like losing my data due to Blogger hiccups. Or maybe I should write up my posts in another editor, then copy then to Blogger. This only works if the post is just plain text. It is not as easy when you have images and URL links in the post. I just wish Blogger could be stable enough to not lose my data. Yes I understand it is a free service. But at this point, if it keeps losing my data, it is worth less than free to me. Know what I mean?
P.S. While I am ranting about Blogger, does anybody else find the auto complete function in the labels edit annoying?
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...