Comments on: 10 C# Shorthands that improve productivity

By: pankaj

pankaj — Sun, 10 Apr 2011 23:28:41 +0000

hiiiiiiii very nice post.learned some new things.thanks

By: Prasetiawan

Prasetiawan — Wed, 19 Jan 2011 09:53:47 +0000

I love the programming and am very happy to visit your website. I will make your website one of my reference website to learn programming. thank you very much for this article helpful articles. Regards,
C Programming Blog

By: Moutasem Alawa

Moutasem Alawa — Wed, 06 Oct 2010 06:56:44 +0000

Thanks for sharing, the one thing i am stunned about is Null-Coalesce operator is totally new for me.

By: Rarius

Rarius — Wed, 01 Sep 2010 15:08:19 +0000

Speaking as a software engineer of over 20 years experience, I hate coding shorthands. Time and again, I have found that they make code less readable and while they may make the initial coding faster (slightly), they have a much larger (detrimental) impact on code maintainability. Code should be written on the assumption that some poor programmer (usually you!) will need to read and understand the code sometime in the future, usually after all knowledge of the code has been forgotten.

IMHO the conditional evaluation and null-coalesce operators should never have been allowed in C#. The longhand for both of these operators is much clearer and takes only a few seconds to type.

While I think many of the other things described above are very useful and laudable (“using” for example) several of them as pure lazyness laying the code open to misinterpretation. This in turn impacts maintainability.

By: josh

josh — Mon, 21 Jun 2010 21:08:04 +0000

Why do

int max = (x > y) ? x : y;

instead of

int max = Math.max(x, y):

By: Coder

Coder — Fri, 11 Jun 2010 02:25:53 +0000

Hey thanks for posting this, although I now prefer C++.

By: Charles Boyung

Charles Boyung — Fri, 21 May 2010 21:02:09 +0000

#8 is a horrible thing to do. That item is a case of pure laziness and leads to less readable code in the long run. Usability is something you can strive for IN your code as well, not just with the resulting interface. And as the name of the usability book suggests – “Don’t Make Me Think”. Why make the compiler and future maintainers of your code try to figure things like this out when you can very easily just define the type right then and there? Only valid reason is that you are too lazy to do it the right way.

By: Rocky Madden

Rocky Madden — Mon, 08 Mar 2010 16:44:23 +0000

Nice write up. I love short hand approaches to make every line of code count. I was unaware of the LINQ statements, thanks!

By: Nick Olsen

Nick Olsen — Fri, 26 Feb 2010 00:16:52 +0000

Good info. Didn’t know about the ?? operator.

Always looking for ways to reduce the number of characters I have to type!

By: juharr

juharr — Mon, 15 Feb 2010 17:55:15 +0000

Wow, I use all of these except for #5, just never found the need. And for #10 not only do I use that, I also wrote a little extention method (those should be on the list) to make it work the way I want it to

public bool IsNullOrEmpty(this string s) { return string.IsNullOrEmpty(s); }

This way I can have

if(myString.IsNullOrEmpty())

instead of

if(string.IsNullOrEmpty(myString))

which I think is more readable and more natural with intellisense.