Just some thoughts

By incident I stumbled accross the book “Clean Code: A Handbook of Agile Software Craftsmanship” by Robert C. Martin. In this book there is a section on exception handling which is a worthwhile read. It states some obvious things – like handle exceptions there where you know what to do with them — but it is good to be remembered by these best practices once in a while…

One of the more interesting things in that section I found the usage, or better should-not-usage, of null values. Return null is typically a sign of something that doesn’t work. Returning null values clutters op code with all kinds of “if null” checks. Moreover, who hasn’t seen a NullReferenceException lately? Instead of returning null, a number of alternatives can be thought of:

First, if the null is actually the result of an error conditions, throw an exception containing thate error condition. If the error is actually based on a deeper lying exception, simply don’t handle that exception and have it bubble upwards. This way it is clear to the user of our object/method that an error condition has been met. Moreover, the exception should contain the necessary information to aid the programmer in preventing that condition.

Second, if the null value is the result of an expected situation, implement the “Null Object Pattern”, or “Special Case Pattern” instead. Using these patterns you return an object that implements the expected interface, but which implementation is empty. For example, a search for files in an empty directory should return an empty list instead of null. The empty list can be iterated, checked for presence of files, but does not have to be explicitly checked for null.

Developers have been a major audience for Microsoft’s SharePoint team. Developing for SharePoint 2010 got a lot easier. An incomplete list of features added to aid developers: Read more

During my work I got confronted with Wordle. A colleague used Wordle to show what a specific website was about. I got interested in how these beautiful word clouds were made and if I could add them to my own website.

Regrettably, the Wordle algorithms cannot be shared by the author because of intellectual property reasons (IBM owns his work). Given the popularity of Wordle, I found it strange that no WordPress plugin existed that would generate similar word clouds. Searching the web for similar algorithms didn’t provide me with much answers either. But hey, how hard can it be? I decided to have a go at it myself.

Read more

I have been wondering how to keep the tags in a blog to describe its content accurately. As I’m not the most disciplined person, tagging posts correctly and precisely is not what I’m best at. During my work I encountered someone who had made use of Wordle. He used Wordle to quickly analyse the contents of a website. The result was great. Simply counting the words seemed a simply and effective way to accurately describe the contents of a site.

So I ended up creating two plugins: one for creating tag-clouds that have the “Wordle” look and feel, and one for “tagging” posts, simply by enumerating all used words in a post. The first is described on an other post: ImageCloud plugin. The second has become the “text2tag” plugin.

The text2tag plugin can be downloaded from WordPress: Text2Tag.
Read more