I had one of those 'wow that's cool' moments last weekend. This sounds really sad and you may think that I need a life, but I was playing with the code for a basic singleton pattern found at:- http://www.dofactory.com/Patterns/PatternSingleton.aspx I ran it with VS 2005 and stepped in to the code. I...

While reading Joshua Kerievsky book "Refactoring to Patterns" could not go silent about abuse of Singleton pattern he described. The question that was asked in the book "When is a Singleton unnecessary?" - "Most of the time". Honestly, I can recall at least a few times when...

The Useless Introduction You Used To :) This post has taken so long to be started in writing. I’ve been busy with many events in my life lately. Suffering from frequent limited internet access lately, and, all this moving between companies thing has been eating me. And yes, I admit, I' have been as tired...

Following on from Justin Etheredge post about becoming a better developer, I would just like to add my nuggets of info. I find that it is very easy to get swamped by the amount of info out there just on .net. I am currently following three simple practices at the moment; set clear goals, refine a topic...

Design Patterns Via C# 3.0 View SlideShare presentation or Upload your own. (tags: design patterns ) Yesterday was my 2 part session about Design Patterns as part of dotNETwork 7th gathering . Thank you all guys for being there, There was so much interesting stuff about the audience. The conversation...

dotNETwork, the most active offline user group in Egypt is having its 7th gathering next Saturday, August 30, which will have two parallel tracks for the first time in the group gathering. BizTalk Introduction, and C# 3.0 Design Patterns, which I will be delivering! If I were you to attend the event...

A few days ago read in Larman's book about Command-Query Separation Principle. Funny to mention that I heard about the concept many times ago, but this is the only source that stated it as a principle. And it makes total sense once you evaluate all the pros and cons of the idea. What's the principle...

In a multi layered application architecture, loosely coupled code is more than a important. It's the basic which can either help the entire project progress, or drive it down the slope to the end (in the bad meaning of the word). One of the basics to keep coupling as low as possible is Inversion of Control...

Mr. Mo has wrote a nice post about securing collection and turning it into an immutable object. I am adding my 20 cents by reminding a great example JP Boodhoo has showed during his "Nothin But .NET" training session, leveraging ReadOnlyCollection<T> class to make a collection immutable.

User Controls are handy when working in web forms, but what a mess they can generate. I was asked what to do when UCs are used and some dependencies need to be injected during the construction - but UCs are a bit tricky in regards to construction. So the possibilities are: 1. Use new operator and instantiate...