7
May

Murphy’s Laws of .NET

   Posted by: Firoz Ansari   in .NET, ASP.NET, Fun & Humorous

I have written Murphy’s Laws of .NET based on my previous experience with .NET (using VB.NET & C#):

1. When coding .NET application, whatever happens, behave as though you meant it to happen.

2. When you get to the point where you really understand those new features of .NET, it’s probably obsolete.

3. For every feature in .NET, there is an equal and opposite malfunction.

4. There will be six ways to do same thing in .NET, and you always discover that you have choose the worst one, but only at the final stage of project.

5. A .NET program will always do what you tell it to do, but rarely what you want to do.

6. He who laughs last probably uses simplest architecture of developing .NET application.

7. A complex .NET application that does not work is invariably found to have evolved from a simpler VB 6.0 system that worked just fine.

8. The number one cause of any .NET based problem is another .NET based solution.

Do you identify yourself somewhere in these laws?

This entry was posted on Sunday, May 7th, 2006 at 4:39 pm and is filed under .NET, ASP.NET, Fun & Humorous. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

6 comments so far

 1 

In .NET – if you don’t know what you are doing, any road will get you there..
;-)

May 9th, 2006 at 10:48 am
 2 

Ah dot net. The solution to, and cause of, all of life’s problems.

May 9th, 2006 at 11:16 pm
Scott
 3 

In Russia,
.NET codes YOU!

May 19th, 2006 at 9:24 pm
 4 

Scott, very true!

May 20th, 2006 at 5:14 am
 5 

Emazig!

June 3rd, 2006 at 10:14 pm
nice
 6 

whatever we sa abt .net, but still we r workin in this domain…& we lov it

June 17th, 2006 at 5:26 am

3 Trackbacks/Pings

  1. Jeff Schumacher    May 07 2006 / 6pm:

    The truths of .NET…

    Firoz Ansari has a excellent, and amazing accurate, post titled “Murphy’s Laws of .NET”
    I think I can identify with #4 the most. :/

    Edit n Place ……

  2. Lazy Developer : Murphy’s Laws of .NET    Nov 22 2006 / 4pm:

    [...] Wednesdays break with a bit of smile. Some time ago, a few months in fact, Firoz Ansari has written on his blog Murphy’s Laws of .NET. I think it is worth to remember is someone didn’t see that already (like me). There will be six ways to do same thing in .NET, and you always discover that you have choose the worst one, but only at the final stage of project. That is my favourite. So true. Filed Under A bit of smile     Rate this post: [...]

  3. Web Links 11.26.2006 « Rhonda Tipton’s WebLog    Nov 27 2006 / 12am:

    [...] .NET Development Passing DateTime Values Through GridView HyperLinkField Limitations of ArrayLists in VB.Net Asp.Net Tools for Developers Murphy’s Laws of .NET Common Pattern For Working With IComparer Asp.Net Performance: Use explicit cast instead of using Eval Common Pattern For Working With IComparer Improved IsNullOrEmpty Extension Method Enumerating Sound Recording Devices Rendering ASPNET 2.0 Button Control-input type=”button” Kudos – .NET Rocks Agile Panel from TechEd Europe Tip/Trick: Registering User Controls in Web.config [...]

Leave a reply

Name (*)
Mail (will not be published) (*)
URI
Comment

*
To prove you're a person (not a spam script), type the security word shown in the picture. Click on the picture to hear an audio file of the word.
Click to hear an audio file of the anti-spam word