Store and Forward

One of the reasons I started this blog was to give me a place to put updates things I publish elsewhere.  I have discovered that web-based journals can be almost as difficult to get updated as printed journals and yet I have no shortage of updates I need to make.  On the one hand, there are the usual typos and clarifications.  Other times readers send questions that would add to the discussion but the articles have no online feedback like a blog does.

The other reason I need this vehicle is that security practices are ever changing.  The developerWorks journal is a great place for the kind of articles that I write because of the very broad and deep readership it enjoys.  I am privileged to be able to contribute for that audience and within that community of authors.  But the articles published there capture security practices as a snapshot in time.  The more specific the article is in terms of providing technical configurations, the more likely it is to need updates sooner rather than later.  This is true of security in general but especially true in the case of WebSphere MQ security, simply because the field is changing so fast right now.

Going forward, I’ll post a blog entry for each new article.  Feel free to make comments or ask questions about the articles through the blog.   As I have updates, I will update the blog post rather than make a new one and in this way we will capture the history and discussion in one place.

If you wish to subscribe to these posts, I will use the categories “Publications“.  When and if there are any errata to report, I will add the category “Errata” when I update the post.  I will be creating placeholder posts for past articles shortly.