How people see the work of a Professor

(I’d love to provide the attribution for the image but I’ve no idea who created it, if you do please let me know; I discovered via Martin Gaedke)

Posted in funny, teaching | Leave a comment

RR: Recurrent Reviewing patterns

Fabiano Dalpiaz describes a list of (good and bad) recurrent reviewing patterns.

I’d add that another “easy” way out for a review, just say that the paper is borderline (and then, if needed, during the discussion phase you can just adapt it to follow the majority).

You can read my other posts on the topic of (bad) reviews here

If you liked this post please consider following my thoughts on twitter and visit my other projects: the modeling languages portal, go wordpress migration services and my stories of a failed entrepreneur.

Posted in evaluating research | Leave a comment

Cite our papers and not only our tools (thanks)

(originally posted in the modeling-languages.com portal)

CONTEXT: In some domains (as mine), many research works end up with a prototype implementation of the research results. This prototype is usually released using some kind of open source license so that the community can benefit from it.

In AtlanMod , we are very proud of the large user base of our tools and of the benefits (and challenges!) that this brings to the team.

However, this has an undesired side-effect, our tools are by far more popular than the research papers describing/introducing them (e.g. everybody in the software modeling community knows ATL ? but, how many could point to the paper that best describes ATL?).

If you are not a professional researcher you may be thinking “so what?”. The answer is easy: the current evaluation system for researchers (I´d say in any country) gives a lot of importance to the number of citations of paper but almost zero to the number of users of your tools. Simply put, a reference to our paper counts for the CV of all paper authors, indicating the url of a tool (even worse if it is just as a footnote or just by mentioning the tool) does not.

I’m not saying I agree with this (leading/creating widely used open source projects should, and can, be quantified and evaluated as part of the achievements of a researcher) but until then please think about us the next time you use one of our tools in your research work. We´ll really appreciate it.

Btw, as Antonio Vallecillo proposed, to help on this, we should make clear ourselves which paper should be cited when using each tool.

If you liked this post please consider following my thoughts on twitter and visit my other projects: the modeling languages portal, go wordpress migration services and my stories of a failed entrepreneur.

Posted in doing research | 2 Comments

RR: 10 easy ways to fail a Ph.D.

If you are now a PhD Student, don’t miss Matt Might’s list of 10 easy ways to fail a PhD. I couldn’t agree more with all of them!

My contribution to the list is the following: Remember that your supervisor for sure wants you to be successful (if you publish more, he publishes more) but this doesn’t mean that your objectives are exactly the same. Yours is finishing the PhD ASAP, his is to get as much publications as possible so he may try to push you to publish more than strictly necessary to finish the PhD (who knows where you’ll end up after?). Of course, this does not apply if you’re one of his PhD students, in that case, he will also be interested in you finishing ASAP so that he can claim that he has successfully supervised PhD students.

If you liked this post please consider following my thoughts on twitter and visit my other projects: the modeling languages portal, go wordpress migration services and my stories of a failed entrepreneur.

Posted in doing research | 2 Comments

Nonsense reviews are a global problem…

We have complained before about bad reviews (e.g. here and here) in the research world but clearly, this is a global problem that affects all kinds of review/recommendation sites.

As an example (via @zef and @drbernhard) the best book review I’ve seen so far (buys a book to learn C and complains that the book talks about “crazy” concepts like Integer and main). Of course, this guy is just a troll but this does not change the fact that his review (i.e. the rating he gives) counts and influences the global perception of the people that is considering the purchase of the book.

I’m afraid we would need a “review police” but of course, then who will protect us from the police?

If you liked this post please consider following my thoughts on twitter and visit my other projects: the modeling languages portal, go wordpress migration services and my stories of a failed entrepreneur.

Posted in evaluating research, funny | Leave a comment

A must-see video if you want to get a PhD in (Theoretical) Computer Science

So you want to get a PhD in theoretical computer science
by: econ101

http://www.xtranormal.com/xtraplayr/7520547/so-you-want-to-get-a-phd-in-theoretical-computer-science

Posted in doing research, job | Leave a comment

Do not cite bad papers (if possible)

Post inspired by this tweet: @worrydream: Citing bad papers encourages bad papers. Don’t struggle through a bad paper, ignore it

Of course, I agree with the “spirit” of the idea but as usual, its practical implementation is more difficult than it seems:

  • PC members (i.e. potential reviewers for your paper) may get very angry if your paper is related to their previous work and you don’t cite it (whether it´s a good or bad paper). I should add that apart from citing it, you should do it in a very polite way, explaining why yours is better but without criticizing too much
  • PC members may know popular bad papers without being aware they are bad. If you don’t cite them, they may think you are missing important related work (it´s completely unrealistic to assume they will check themselves whether you´re not citing one specific paper because it´s just crap). You should cite all well-known papers in the area regardless their quality.

Of course these two reasons favor the citing of bad papers which only aggravates the situation but nobody said life was easy!

Let me just add that bad papers are another reason why evaluating the work of a researcher based on the number of citations he/she gets is a very bad idea.

If you liked this post please consider following my thoughts on twitter and visit my other projects: the modeling languages portal, go wordpress migration services and my stories of a failed entrepreneur.

Posted in doing research, evaluating research | 2 Comments