Wednesday, May 5, 2010
0 Blog 2.0: Baby's Got A Brand New Blog ...But the URL is the Same. :)
To the several GoogleConnect Followers (who were following at the old blog), please read this post (i.e.,click blue link) to view an important update about your subscription to "Cooking with Corey." It might explain why you are no longer seeing any of this blog's content from within Google Reader. :)
So, this also explains why this blog not only looks a bit different now but also functions a whole lot better too. :)
--"Reactions" checkboxes: You might notice that the "Reactions" checkboxes now appear at the bottom of each post, (like it does for almost all of my other blogs), as well as the AdRoll square for sponsors on the right-most sidebar. Neither of these features had been showing up in the old blog version, even though the corresponding HMTL/CSS code for both entities had been clearly visible in Blogger's editing tools. [And, in the former case, I could even configure the "Reactions" settings from within the "Post" page element (in the "Layout" view), but then nothing would display on the blog itself!]
At long last, I bit the bullet and created a new blog, which would automatically contain this new, condensed & updated CSS code, as well as several completely new pieces of CSS code. The new blog template's code is much improved, and contains several new features, thanks to the updated code contained in the latest Blogger templates.
And finally, no matter how good the software or the software engineer is, sometimes these things just happen; it's next to impossible to foresee every possible scenario or technical issue. Sometimes a bug passes by unnoticed and needs to be patched as an afterthought. That's just the way it is.
You can often tell who codes and who doesn't just by the way they respond to these types of issues. :) The nice thing about software engineers, sys admins, and other technical folks is that they are solutions-focused. Instead of complaining about their technical problems, they hone right in and try to fix them. :) They also know that sometimes there are no instant solutions or immediate answers.
I always find it funny when users think that a technical person should immediately know the answer without first examining the issue at hand. We technical folks are no different than anyone else that way: We typically need to see what's going on up close and analyze the situation, unless the problem described to us is one that we've seen a hundred times before. In this way, we are no different from anyone else.
Try coding or fixing a computer sometime and you'll gain a better appreciation for the process. :)