C# 4.0

Anyone seen the new C# 4.0 features? (Examples can be found from the C# October 2008 CTP page).

Well done on (still) copying Python (and other related dynamic languages) into your so-called statically typed language.

You guys make me proud.

Programmers: far more than typists

typing

I recently read a post by Jeff Atwood where he states that programmers are typists first and programmers second. This is something that I could never agree with.

I am a Software Developer. I should be part of the whole development cycle. That means, among other things, I design, write, test and maintain my own and other people’s code. The initial coding is possibly not more than 20% of the full cycle. In fact, according to this post by Peter Hallam, it is no more than 5%! How then can we possibly be typists first and programmers second?

A programmer is not a cog in the machine; he invents the cogs and arranges them in the machine. He is not a factory element; he is the one building the factory. Sure, there are different roles and requirements, but this is what developing software is all about.

Yes, I agree that typing is one of the fundamental requirements for programming, but a programmer is so much more.

To agree with Jeff, if you do not know how to type, it is not really that hard to learn. Get yourself a typing tutor and invest some time in practicing. However, the day programmers become nothing more than mere typists is the day I leave IT.

True Sceptic, or Noisy Idiot?

blogging

More and more sceptical websites seems to be appearing all over the internet. This in itself is a good thing, but how many of them are truly sceptical?

It is easy to take on a topic that is black and white, right or wrong. One must be willing to question public opinion and do a lot of research, but in the end, there usually is an absolute answer.

The biggest challenge lies in grey areas: there where there seems to be no absolute right or wrong answer and even if there is, it is rather hard to prove. This is the true test of character.

The reason for raising this issue is that most people, when faced with an uncertain challenge, fall back to personal beliefs and convictions. I have seen many of these websites, filled with fallacies and mockery. Sometimes it is fine to use mockery with an abundance of evidence, but still, since mockery is an attack of the person rather than an attack of the argument, it is something of which most scientifically minded people should never make themselves guilty.

To all those people who like hearing the sound of their own voice: just because your opinion differs from that of the public does not suddenly make you sceptics. I think it is best that I do not provide links to any of these pages.

As an example I will point to Brian Dunning, from skeptoid.com, who did a podcast with the topic Who kills more, religion or atheism. Most people would rather choose to avoid this topic, and those who do talk about it usually do so out of anger for the other side. I must say that his opinion is the best answer I have ever heard on this topic. Listen to (or read) it, and make up your own mind.

I am not against scepticism, sometimes I just get frustrated…

LINQ Quiz

Just for fun, I made a little quiz following my previous LINQ article.

Question 1

What is the difference in effect of the following code sections? Note that “Failed” is a nullable bit, so we will label the states as red, green and yellow (null).

// Option A
where (filter.Failed.HasValue && doc.Failed.HasValue ? filter.Failed == doc.Failed : true)
// && (…) — more filters here

// Option B
where (filter.Failed.HasValue ? filter.Failed == doc.Failed : true)
// && (…) — more filters here

Question 2

What would happen if all the queries ended with “false”?

where (… ? … : false) && (… ? … : false)

Question 3

Keeping both performance and readability in mind, what is the difference between grouping all the queries together (see option A), against having each in a separate section (see option B)?

// Option A
docs = from doc in docs
where (filter.Failed.HasValue ? filter.Failed == doc.Failed : true)
// && (…) — more filters here
select doc;

// Option B
if (filter.Failed.HasValue)
docs = from doc in docs
where filter.Failed == doc.Failed
select doc;
// more filter blocks here