Instead of writing one or two last articles before Christmas, here I am trying to fix a problem with this blog. I don’t know when this started, but right now no articles are accessible, only blank pages are shown. I have no idea what caused this, therefore debugging the problem is difficult, especially since this is on a shared webhosting account, where I don’t even have access to the error logs.
Interestingly, the RSS-Feeds and static pages are still working. Anyways, I apologize for the inconvenience and hope to have this fixed soon.
UPDATE: I was able to fix this by deactivating my comments-plugin. Sorry for the noise.
Once again, it is time for a short newscast. Notable this time is the fact, that more and more stuff seems to be written about
In one of my last articles, I have told you about the state of affairs regarding
I always like it, when my readers contact me directly. Thats why I have put up a
A little while ago, an event was held by
I just wanted to make anyone interested aware that I have finally gotten around to updating my
There were some interesting articles during the last two weeks, which I would like to share with you (also, I have to compensate for not posting for two whole weeks – my target rate is one post per week and I do want to make up for missing that target for the first time :roll:):
This post serves a triple-role: First of all, it is a vision document for the project I am doing at work right now. It describes the high-level goals for me and the people that will be working on the project with me – saving me from having to explain them multiple times and also providing some focus during the lifetime of the project. Second, it is an exercise on how to write a good vision document. I don’t get to employ my project management skills too often while at the university and I am eager to practice some of the things I have learned from the literature (in this case: from Scott Berkuns excellent book
Before I start, let me say a warm thank you to all the people who have read this blog over the past few month, have left their comments, dropped me encouraging notes or mentioned me in their blogs: I really appreciate your support, thank you!
When I am talking on forums or to some of my students, from time to time I realize that I have gotten so used to expecting a certain vocabulary and certain concepts to be known to others that it isn’t even funny. In German we call this being betriebsblind, which basically means nothing more than expecting everyone to know what you know (at least to a certain extent), because the knowledge is so essential for what you do every day. The concept of Thread-Safety definitely belongs into this category for me, as I usually have to force myself to explain it and its implications to my students new to parallel programming, because it seems so trivial. Unfortunately, it is not. Therefore, I will spend the rest of this article trying to explain what Thread-Safety means, why it is important and also highlight some ways to achieve it without throwing your performance out of the window. I would also like to issue the usual warning to my more advanced readers: the beginning of this article is most definitely not for you, the end may be worth checking out as well :P.