Saturday, August 25, 2012

Anatomy of asking a question

image credit
I started my first grad school class this week, and it looks to be a good one. Two lectures a week, a ton of reading, and an hour recitation where we discuss the papers we've read. We're graded on participation, which is pretty much my only incentive not to sit anonymously in the back of the room and doodle. The easiest way to participate in class, besides coming up with amazing insights into the material is to simply ask questions. (Or a question. Let's not get too carried away.)

All of us have had some form of the phrase "There's no such thing as a stupid question" drilled into our heads from a very young age. (Alt: "The only stupid question is the one not asked.") The problem is, in the circle of our peers, there in fact is such thing as a stupid question. But there also isn't. Ok, let's back up for a second. Is there such thing as a stupid question?

Answer: To the people that matter, no. 

If you have just heard something that you don't understand, and you need clarification to understand it, and you ask for clarification, clarification is given, then that was a perfectly acceptable use of a question. 

Caveat: To other people, (hereby known as jerks) yes, there is such thing as a stupid question.

I hesitate to even mention this here, because other people's opinions don't matter, yadda yadda yadda, except in what realm of the universe is this true? (Rhetorical question--and obviously not mine.)

I think we can all pull up some anecdotal evidence of being in a class where someone asks a question the most everyone else in the class already knows, and there's some form of eye-rolling (if you're lucky) or snickering (if you're not) from the back of the class. (My eye roll this week came from someone asking the definition of "-ploidy" in an upper level genetics class. But again, the person that asked the question got their answer, therefore, not a stupid question.) And like most unfortunate things, they are almost always hilarious except when they happen to us. 

Here's what happened to me yesterday.

I asked a question about primer binding specificity and the introduction of bias in the 4C technique of chromosome conformation capture. Follow up question how are they relating sequence read depth to frequency of what's actually happening in the cell. (If you're really interested, we were discussing this paper by Zuan et al.)

Two things went wrong. 

1) I tend to garble my words sometimes when I ask questions in public places like classes or seminar. I just get nervous or something, so instead of saying something calm and relatively straight forward, what came out of my mouth was more like, "Ermmm sequencing bias primers...." And then I sort of trail off expecting someone to finish my thought because right? You know? 

2) This know it all in the row behind me really nice girl sitting behind me because I don't arbitrarily judge people based on whether or not they are very rude immediately interrupts me (to be fair I had sort of trailed off, see above) to say that my question is just wrong because of the restriction digest sites and something else completely unrelated to my question. 

And then the conversation ended. 

Which brings me to the anatomy of asking a question. 

There are two parts to asking a question.

The first is actually asking your question.
Coming up with a question

This may seem kind of silly, but the first thing you need to do is to pay attention enough to know what's going on, so you can ask a question. 

If you've been doing that, congratulations! You're caffeinated! The next step is coming up with a question. This could be something as "simple" as you don't understand an axis label on a figure, or if you don't understand the way someone is using a word, or a technique, or why they chose those controls, etc. If you can do that, congratulations, you've been really paying attention. 

Finally, and this is where I always  get stuck. You have to actually ask your question. You can't just think about your question, you can't just second guess your question (also known as "questioning your question"--this is a very deep and unprofitable wormhole that can only lead to paralyzing insecurity--let's try to avoid this), you have to actually ask your question. If you're me, you will give yourself a pep talk that sounds like this: Okay rachael, deep breaths, slow your roll, enunciate, and make sure your words come out in the right order.

(Also if you are a normal person and have no problems asking questions, feel free to ignore all of this advice, and haha--I don't really need it either I'm just kidding around because who me? I'm not neurotic at all.)

If you get your question out, and for goodness sakes, don't tail off at the end like I do, and don't assume that other people know what you're talking about--also be clear and concise and there are no stupid questions but 90% of the time no one likes extraneous information in questions--it's not over yet.

I think this is what a lot of people forget, and this is definitely what I forgot in my class yesterday, the second part of asking a question is making sure that your question gets answered

I wish I could bold this and stress this so much, because I think while this isn't a problem for seasoned professor that Knows What They Are Talking About, I think it can be a problem for a student that Isn't So Sure About What They Are Asking Thus The Whole Reason For Why They Are Asking it. 

Making sure your question is answered!
The thing that you have to remember is that it's no ones job but your own to make sure your question gets answered. Your question is your baby. No one is going to advocate for it for you. There probably isn't anyone else in your class (unless you're lucky!--more on that later) looking out for you. So here's what you have to do.

You have to listen to the answer. Duh, but this is basic Respect 101 for the person you're asking. But it also can help you. If they misunderstood your question, now is the time to gently put them back on the right direction. In my opinion, you usually get one chance to do this, and you're allowed to do this out loud--it's for everyone's benefit, your own, as well as the audience and the person answering. 

If they still don't answer your question, (and even if they do, but not satisfactorily, or if they do and you have more exciting questions), form follow up questions! But write them down so you don't forget, and I would suggest waiting until after the talk/class in order to ask them. Unless no one else is asking questions, and yours seem like good ones. In which case, go for it. 

Yesterday I pretty much forgot the whole second part of asking a question. I didn't feel confident enough in my question to rephrase, or verbalize why the girl behind me's answer was insufficient and also not related to my question at all, and the TAs weren't about to defend my question either. That was all on me. And this I think is a flaw of classroom discussions. You have to remember that not everyone that sounds like they know what they're talking about actually knows what they're talking about.

Which begs the question (ha!) in the classroom/grad school setting, which is better, misplaced over-confidence, or paralyzing insecurity?

It's a trick question--you really shouldn't ever choose one or the other. The answer is both, and I think the point is to try to live (and ask questions) with an open a mind as possible. 

Last part of my story:

I actually went back to lab feeling kind of shitty about myself after this girl responded to my question so rudely. And I spend the next few hours feeling like maybe I can't hack grad school and why is everyone smarter than meeeeee? But then I (luckily!) saw a guy from class later that evening, and he said that they thought that girl totally missed my point in class, and he had some of the same questions too, and he had wanted to rudely respond to her in class, but then didn't want to be the dude that starts some crazy loud discussion in class. 

Moral of the story--Ask your questions. Advocate for your questions. There are jerks in life. Don't let the jerks keep you from asking questions. And stop calling people jerks. It's not nice. 

Wednesday, August 8, 2012

You know when...

...you figure something out, then you don't use it for a while, and then you have to completely relearn it?

This is me and Endnote. Every six months or so.

So after I figure out Endnote one more time, I'm totally posting a tutorial on here. Purely for my own use.


Monday, May 7, 2012

Abstract clouds

Hey--

So I'm sure you've all seen word clouds ala wordle, where it takes all the text from a word document or webpage and then uses word frequencies to generate a kind of infographic where you can see the most used words, the big ideas if you will. 

Check it--someone made an app that you can input an author, it pulls all their pubmed abstracts, and then you can input that into wordle. It's called pubmed2wordle.

I decided to look up some of the PIs on my floor, in case I'm ever in the elevator with one of them, I can have some talking points. 

For example, 

Wordle: Untitled

I will know to talk about microRNAs with this dude, or

Wordle: Untitled

microRNAs but specifically let-7 with this woman, and also, oh look she works on C. elegans and development.

I think can be a great resource if there's a visiting faculty giving a seminar, or you're trying to pick a lab to rotate in, or you just want to know a little bit more about someone's research without spending hours poring over papers, this might be the first place I go from now on for all those things.

And just to mix it up a little big, because contrary to popular belief I'm not only interested in microRNAs...


Wordle: Untitled

That's my dad. He works on yeast and kinetochores and chromatin and microtubules!

It also makes for an interesting discussion of how much information do we actually need to understand something. And is relying on a tool like this, is that being lazy or being efficient? Obviously, it will never become a substitute for reading papers, but it's a pretty neat tool regardless. 

Do you think you could find yourself using something like this? Could you see yourself directing a student to it?  

Friday, May 4, 2012

Revolution

I predict that within the next 10 years there is going to be a scientific revolution. And it's going to happen online.

Hear me out--(This is sort of like the time that I told my the dean of the med school that I thought that social media and online presence is going to start becoming an issue for faculty seeking tenure and grants. He may or may not now think I am a teenage moron, but I still go out of my way to say hi when I see him on campus.)

But here's the thing. Me, early-20's, bright-eyed and bushy-tailed, and all of my peers are online all the time.

And, as much as anyone would hate to admit, we're the future of science. Logic would follow then, that you would want to reach out to us. Grab our attention. Mold us into images of yourself.

I'm starting to look at grad schools and while that whole subject is deserving of a post of itself, here's what's really frustrating.

A lot of PIs don't update their websites regularly, and that's a problem. Sure I can find someone's most recent publications through PubMed, but what if I can't get to them because of access issues? (I know--this can also be turned into more of an open access discussion too.) One of the nicest lab's I've looked at, the PI had a list of publications and some of them had an asterisk at the beginning of certain citations, indicating that this paper had come from a graduate student in the lab. This is something that I think people need to, if they don't already, take note of. There are probably few better indicators of a productive and plentiful learning environment than if a lab is producing paper. Notice I said a lab. I've started to become wary of PIs that tend towards review papers, or ones where they're part of a larger collaboration and it's only them, and no one else from their lab. (Gosh I want to say something really mean here OHOKAY I'll just say it, those who can't do, review!!) (I'm also acutely aware of the fact that I know absolutely nothing about anything and may all instances of snark and judgment act karmicly against me in later life--there, I said it for you.)

It's all about the internet.

I'm painfully aware that I'm part of this generation-can't-I-just-look-it-up-on-wikipedia, and if I hear one more disgruntled post-doc telling me that when they were in grad school they had to walk to the library and request a journal, I'll write a blog entry about it, but this is the way it is. Let's not fight it, embrace it. It's so hard to grasp for people that didn't grow up with the internet that you can build substantial relationships and communities online. Yeah, the usual arguments of "impersonal" still exist, but more and more those arguments are vastly outweighed by the enormity of good things that come from the internet.

Take my most recent example of photobleaching. I photobleached my cells. I had one meaningful face to face conversation with someone about the fact that I was probably photobleaching my cells, and then I was depressed and went home and went on facebook, and this happened:


Edited for brevity, and in short, I got tons of comments from real live people, all with real live experiences, with their own labs or microscopy facilities. I learned about 'pseudo-live view' and about different types of fluorophores, all on facebook. facebook!

And here's the thing. I do know Wendy and Omar from real life, and hey uncle Ray!, and if I saw them at the grocery store I would definitely stop and say hello (if of course we weren't in different states), but my itty-bitty-in-the-grand-scheme-of-things-although-seemed-like-a-very-huge-deal-at-the-time photobleaching problem was not big enough that I would have thought to pick up the phone and call any one of these vastly-overqualified-to-be-answering-my-questions people. But facebook allowed them to do just that, on their own time. 

The internet is this amazingly powerful beast that I honestly predict is going to allow a lot more people's voices to be heard, scientifically and otherwise. Of course, we're going to have to learn to filter, but you know, you have to filter in real life too, it's not like the crazies only exist on the internet. 

But the advantages: an open access revolution, more transparency about authors on publications, PIs interacting with peers and students online and in real time? Scientific discourse over twitter? Tenure-seeking faculty might poo-poo this now, and half the people in my lab think I'm crazy for even having a blog, but these are really powerful things that the people in academia are going to start to realize are really important to my generation of budding scientists. 

We're young, we're excited. We like to think we're cool, but that's only because we think that being nerdy is cool. If academia can start having real online conversations outside of an ivory tower that I can watch, learn, and maybe even be a part of, well, you'll have my endorsement. Even if that endorsement is in the form of a tweet. And then a grad school application. 

Oh, and update your damn lab webpages more often. 



ETA: in retrospect, everyone in my lab thinks I'm crazy for having blog.

Monday, April 30, 2012

Monday problems

Check on cells or make coffee.
Check on cells or make coffee.

Sit paralyzed at desk wondering whether to check cells or make coffee?

Yep, it's Monday.

Thursday, April 12, 2012

That awkward line between tech and student

The day has come. You're all set up to do an experiment. You've spent days preparing. All of your pipets have been lined up the night before. Tip boxes are full, waiting. Media is warm, gloves are out...and your PI walks by your bench and demands that you attend a seminar with him (or her.)

(Alternate universe: Your PI emails you the week before alerting you of the talk and you're really thankful because you didn't have that much to do that day anyway.)

EITHER WAY--you attend dutifully.

On the way to the seminar (in which you lead the way because Techs Know Everything including all the shortcuts between buildings), your PI reveals to you that the seminar speaker is a moron, has submitted a moronic paper to a moronic high profile journal, in which your PI is in the middle of reviewing. But of course he doesn't want to affect your view (yeah right) but instead wants your thoughts on the talk afterwards. (No pressure!)

Tech-PI relationships are a funny beast. It's a fine line between employer-employee (which it is at face value) and mentor-mentee (which it may evolve into). Each has it's own unique sets of issues. I'm in the lucky situation where my PI knows that this job is just a step in the direction of a career for me. He knows that I'm probably going to be leaving soon to go off to grad school in...something, or try to move up and out into a new position...sometime. When your PI knows that, and better yet, respects that--that's when you can start pushing the boundaries of employer-employee into mentor-mentee territory.

However, a big thing to keep in mind is: Cave Canem...ma.

source
Or, for those not well versed in Latin/English (Lat-glish?), beware of dogma.

I think a lot of scientific disagreements, the higher up you get on the ladder, tend to be fueled by competition and ego more than anything, while the differences are more or less just differences in dogma. But vastly different ways to look at problems are more or less what fuels scientific discoveries. I mean, someone has to be thinking outside of the box. I guess if you're the tech you just hope it's your PI.

It's a funny thing...and I'm having trouble writing it now because I'm trying to say it as delicately as possible, but keeping an open mind is the most important thing you can do in this situation. (Apart from staying awake during the actual seminar. Obviously that is priority numero uno.) At this very very very early stage in my career, the most important thing I can be doing is looking for places to think critically. Both of my PI and of his competitors. It's not always easy, and it's obviously very important to keep in mind who's grant you're being paid off of, but it's also really important to remember that thinking critically about something is not synonymous with criticizing it. And dogma and broad generalizations and effective public speakers get funded, because sometimes making things seem black and white is the best way to make sure your research gets noticed...but that's not I as a tech or a student, or whatever weird limbo position I'm in now as I'm starting to have my own ideas and taking ownership over my own research...that's not necessarily the position I want to be stuck in.

I wonder how other people in my position deal with this kind of thing. Thoughts?


Tuesday, April 3, 2012

Adventures in photobleaching

There are a couple of ways to act when you make a Really Big Mistake in lab.

1) Correct it, tell no one, and pretend it didn't happen. This method is preferable when you do something small and stupid. Like one time some sequencing results didn't look very good. And I realized that I had completely diluted my primers to the wrong concentration. Like, mMols off. This would be an okay mistake not to tell anyone else around you in lab, just as long as you fix it and make sure never to make that mistake again. (And also that no one else will be using your primer stocks.) (This also isn't exactly how it went for me because it took someone else pointing out that I had made a blaring error in my primer dilutions, so everyone knew about it in the end.)

2) Admit you made a mistake, ask for help, correct it, and then pretend it didn't happen (but never make that mistake again.) This method is especially useful when something big is going wrong, and you can't figure it out on your own. This is when you just have to suck it up that you'll look like an idiot for about 5 minutes while someone is explaining what you did wrong (or as I prefer to see it, what you weren't doing right!) but in the end it's all for the best because a) hopefully you learned something, and b) you won't make that mistake ever again. And it's a win-win! Because when you come across another poor soul who's made the same mistake as you, after you help them figure out what they weren't doing right, you can choose whether or not to admit to them that you too made the same mistake.

3) Ask for help, figure out that you were a complete idiot about something, and laugh uproariously about it. This might include just yelling PHOTOBLEACHING every 20 minutes or so for the rest of the evening after you figured your problem out. 


So this may or may not have happened to me today.


I will start off by saying that my lab does not do fluorescent microscopy. No one in my lab has fluorescent microscopy experience, and so we're looking at some fluorescence in our cells (just to check transfection levels) and using a scope in a lab downstairs that we've never really been formally trained on. The one caveat is that I come from a family of fluorescent microscopists--so this what follows is sort of unforgivable.

Here is what happened.

We walked downstairs with our little flasks of cells, and we put them under the microscope. We turned on the light, turned on the laser, made sure we were on the right filter, opened the shutter, and looked at our cells.

"Ooh!" My post doc says, "Pretty glowing cells!"

"Awesome," I say, "Let's put it on the screen!"

(I am clearly paraphrasing here.)

So, with the fluorescence still on, we manually switch the scope from eye to camera, we press "Live", and we wait for the picture to come up on the screen.

(If you're keeping tally of time blasting cells with fluorescence, we're now clocking in at 2 minutes.)

It takes another few seconds for the image to come up, then of course we have to refocus slightly for the image to be in focus for the camera.

Then we take a picture.

(Fluorescence still open, in case you were wondering.)

Then we hmmm and hawww and write down the settings we used so we use the same settings for all the other flasks.

Then we go get another flask.

I will skip the rest of the nitty gritty details, because the short of it is, we kept looking from eye to camera and back again, and since apparently neither my post doc nor I were feeling incredibly competent today, we kept forgetting to manually change the scope from eye to camera, all with the fluorescence on. 


And then we wondered aloud to each other, "Why are all of these flasks getting progressively dimmer?" And of course, being scientists, we say, let's get that first flask out that was really bright!

So we get the first flask out and everything is really dim.

In retrospect:

It didn't even occur to me that this was the problem until later I was talking about what I was doing to someone who actually knows how to do microscopy, and they were just like, You focused with the fluorescence ON?? My post doc still isn't quite convinced that this is the problem, but I think she just doesn't want to admit that it's the problem because it makes us look like complete idiots.

And me?

I am perfectly ok with looking like a complete idiot. Because, you know, how else would you learn? (By actually listening carefully to what people tell you to do so you never make mistakes? Where's the fun in that?)

And for the rest of the evening, yes, I have yelled PHOTOBLEACHING aloud at odd intervals. Because, arrrghhh.....PHOTOBLEACHING!