Link Details

Don't see what this has to do with software engineering. And why link to a blog entry with a brief summary and a link to the real story? Why not just link to the story itself?

Nick,

I see how you feel. I felt the same way when I first read the research paper. Then, I read carefully. There are so many companies out there currently that are looking to enhance their productivity through all means available to them. When you look closely, Tim Welsh has mentioned some excellent tips for companies (needless to say, including IT companies). There are some of us who saw that and voted up. After all, it's a research paper and needs a careful read, I understand.

It's good to have a wider perspective than just focusing on, for example, "how this while loop is working" these days for IT programmers. Conferences are focusing on that, businesses are looking to get more value from their employees, and that's how I feel IT people can overall get "more recognized" at work places. But, I see your point too.

Thank you for your comment.

Best regards,
Abhay Bakshi

No, its not a research paper. Its a very short blog entry about an article about a research paper that doesn't really say a damn thing other than a brief summary of the results (which one could of gotten by reading the article itself, or presumably from the research paper's abstract had it been made available). No analysis, no details, no explanation for how this applies to the IT world (which is not obvious as most developers work in cubicles which limit your field of vision in the first place). Had you submitted a link to the paper itself or even to just the press release, or a substantial blog entry that actually brought something to the discussion, that would be different.