tag:blogger.com,1999:blog-17226356.post6663155524746881874..comments2023-10-25T07:42:21.149-05:00Comments on Average Professor: People who are not my problem.Average Professorhttp://www.blogger.com/profile/13879007878874956437noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-17226356.post-21813554801038535972008-02-17T22:32:00.000-06:002008-02-17T22:32:00.000-06:00I totally get the sad faces. BUTDO NOT feel bad ab...I totally get the sad faces. BUT<BR/>DO NOT feel bad about saying no to this person! <BR/><BR/>Like god, we should only help those who are at least trying to help themselves!<BR/><BR/>I'm kidding, but only sort of. You have got to protect your time from leeches. This person is a leech. <BR/><BR/>What scares me about leeches is that while they are too lazy to do it themselves, they sometimes get desperate and cheat. <BR/><BR/>But again, that is NOT your problem. It's the ethical obligation of the person who brought him in and his co-authors' responsibility, if they ever get to the point of publishing whatever gets cooked up with this software. <BR/><BR/>Unlike what principle investigator said, I would steer clear of this person. It sounds like this software is involved enough that even if he goes through the manual and does the exercises (both of which sound unlikely), he will be leeching off you for quite a while. <BR/><BR/>The only advantage I can see to this is that, if he turns out to be a good student when he applies some effort, you might learn a few things in the process of teaching him. But it really depends on your level of commitment. This is where the borderline gets fuzzy between "good deed" and "co-author", because if he needs that much help, you're bound to end up doing at least half his work for him. <BR/><BR/>Beware.Ms.PhDhttps://www.blogger.com/profile/06542602867472447035noreply@blogger.comtag:blogger.com,1999:blog-17226356.post-48360358804760182402008-02-17T20:41:00.000-06:002008-02-17T20:41:00.000-06:00What principle investigator said. The only excuse ...What principle investigator said. The only excuse for his not trying to figure it out by using the help you've already given him would be, if he hadn't realized it wouldn't be just 5 minutes for you to "make it run." This should be clear by now.Schlupphttps://www.blogger.com/profile/16399256701731431557noreply@blogger.comtag:blogger.com,1999:blog-17226356.post-91760287425507922872008-02-15T15:43:00.000-06:002008-02-15T15:43:00.000-06:00Well, it seems to me that you have already offered...Well, it seems to me that you have already offered help (the shared exercises from your workshop). So unless this postdoc takes advantage of that help, he does not deserve more of your time. I would have no qualms about instructing him to read the manual and do the exercises and then come back to you if he has specific questions (with the warning, of course, that you yourself are not yet completely fluent with the software).Katemonsterhttps://www.blogger.com/profile/08996019407978388758noreply@blogger.com