Software. Efficiency. Scalability.

Lately, my news feed and I have been out of touch. Let me elaborate.

Most of the links I’ve seen recently could be put into two large categories: “mobile phones” and “I wonder what people smoke”.  I am not a mobile developer and while I keep an eye on the mobile world, it’s a bit outside of my area of expertise. Most of the other stuff … well, I am not even sure what to tell you. It’s illegal to have weed this strong here.

For instance, one of the blogs I follow is Jason Haley. He posts links to other blogs, calls it “Interesting Finds”. One of the sub sections is called “Code to look at”. Well, take look at the today’s catch:

1) Fluent.Xml.Linq – Exploring the limits of C# syntax.

Not sure why it has XML and LINQ in the title. The article is about 5 different ways to include HTML in your C# code. Maybe it’s just me, but I have never ever needed to add HTML to my C# code. Sometimes I need to add code to my HTML (to control its generation), but never the other way around.

The brightest part of the article is a quote by Martin “UML” Fowler: One of the problems of methods in a fluent interface is that they don’t make much sense on their own. Isn’t it shocking? Fowler says there is a problem with something that doesn’t make much sense! Who would have thought.

2) Yet Another Singleton Implementation in .NET 2.0

In the very first sentence the author asks the most important question: Many of you aware what is Singleton Pattern is. For whom don’t know what is Singleton pattern is?

Lucky, Bill Clinton has already answered this deeply philosophical question back in his 1998 Grand Jury testimony: It depends on what the meaning of the words ‘is’ is.

3) JavaScript code to determine when DayLight Savings Time (DST) occurs.

This article gets you one Google question closer to the solution for a problem you are unlikely to have.

4) FileSystemWatcher – Pure Chaos (Part 1 of 2).

Yet another background thread that monitors file system changes. It’s been in WIN32 API since, well, WIN32 API. Thrilling.

5) User Story Source Code Layout with MSpec.

public class I_transfer_an_amount_less_than_my_savings_account_balance

Naming_classes_like_this_is_bad_for_your_Karma.

Seriously. Never ever name classes like this. No matter what the reason is.

6) Diagnostic Trace Display Using WPF.

A 10 line System.Diagnostics.TraceListener implementation.

Have a nice day!