Recently I run into another case of developers who are confused by all the static vs. dynamic and weak vs. strong type system classification. And you know what?  This is actually OK. Usually one can be a good developer in one type of language and understand how it works without knowing all the kinds of type systems and the terminology of the subject. However I still find it useful to try to explain it even though there are other and probably better resources out there. It is especially useful since most of my readers use C# and C# developers can benefit the most from this knowledge because C# combines several typing approaches...

   For years I have thought that software development is very similar in feeling to archaeology.  As a software developer you get to work on that legacy project that is ancient. The ancient developers are gone and you are on your own...

   It is the 256th day of the year again which means that everyone whose job is to create bytes that move other bytes around can celebrate.

   I remember several years ago the Wikipedia article for Programmers' Day was created and deleted and then created and deleted again. There was a heated discussion if the holiday really exists. Some people said that their companies observe it and have some related activities therefore the holiday is real. However others pointed out that someone can invent a holiday like this one and put it on Wikipedia to give it credibility so the article should not be allowed. Luckily the holiday was accepted as official professional holiday in Russia which gives it enough physical world credibility so the article is now up again.

   Let the celebrations begin!

   Here is part 3 of the Java vs. C# series which should have been called "Why C# Is Better Than Java". I remind you to read part 0 in order to get familiar with the motivation behind the articles. Part 1 and part 2 are also recommended...

   C# has a lot of features that are kind of obscure but are really cool when you need them. When I was young and reckless I once declared one particular C# feature stupid and useless. Less than a week later I had to use this feature to avoid writing some ugly code and realized how useful and deep the feature was. Since then I have learned not to question Anders's (Hallowed be His name!) wisdom even when I do not understand it. A few days ago I was astonished to find a new use for another feature that I thought I fully understood. According to the C# designers when they evaluate a feature they favor features that have multiple uses over features that solve only one problem. It seems like I underestimated the C# team once again and by now I should have known better. The feature in question is explicit interface implementation...