A few days ago I was asked how one can develop a page in ASP.NET Web Forms that fulfills the following requirements:

   1. The page should display a product.
   2. There should be an AJAX pager (next/previous or normal pages).
   3. The user should be able to copy URL from the address bar and send it to other people who should see the same product.
   4. If the user pastes the link in Facebook the right product information should be displayed.

   So how can we fulfill these requirements using good old Web Forms with update panels...

   I almost forgot that today is the 256th day of the year which means that it is Programmers' Day. Happy holiday to everyone cranking code!

   I almost forgot because of all the excitement around BUILD. Be sure not to miss the live stream tonight (it should appear on the site) and learn about the future of Windows. A nice day for a big dev conference. Good job Microsoft!

   I believe every developer has been in a situation where the software behaves in a way that just cannot be.  Every developer has applied fixes that do not make sense and he had no idea how they worked. Recently I came across the most brutal version of "cannot be" I had ever encountered while working on software...

   Before I unveil the atrocities of the String class in Java we are going to do a simple test. In order to get the most accurate results from the test you should try to do it as if it was a normal task at work. By the very fact that you know this is a test you will probably not do it like it is a normal task at work but at least try not to read the source code of the Java methods you are going to call. So here is the task – Write a method that given a string replaces all the occurrences of the substring "…" with the string ",,,". For example given the input " a.,...b...c." the method should return "a.,,,,b,,,c."...

   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...