Showing posts with label assistants. Show all posts
Showing posts with label assistants. Show all posts

Thursday, June 27, 2013

Dare the plane to crash, redeem the miles for cash when it starts to dive

The people who do the neuroscience are the least appreciated and nurtured resource in science.

Here's why:

We never bothered to map out success.
Few labs have documented, readily available, and shared protocols. This usually means that people learn technique from an oral tradition. Strangely, oral tradition is an inexact method and seldom lends a deeper understanding of technique that a career scientist needs to troubleshoot, should things go awry (as they usually do).

Superiors/senior scientist advisors seldom establish clear goals for success for more junior scientists. Sure, projects come and go, but more long term goals (18- or 24-month long, or even 4- or 5- year long career-related landmarks) might lend better career perspective for scientists who frequently can't think far beyond the current experiment.

We expect a level of devotion that's religious to qualify for respect.
Unless you're an undergraduate (and sometimes even that won't help), your PI expects you to be at the bench during business hours and toiling on everything else before and/or after that work. Usually more.

People who pass on family commitments or personal needs in the name of scientific work wear these sacrifices like a badge of honor, whereas someone who strives to achieve a work-life balance is considered less dedicated.  Recently, a co-worker of mine declared that they had to leave work early, at 5 p.m., to "babysit." I couldn't help but scoff. "I don't think it's babysitting if it's your own child," I mused.

I've been involved in roller derby since my third year of graduate school (that's nearly four years, including the two years I've been in my postdoc). Both of my superiors have reacted to my involvement in that community like it's the most insane thing they've ever heard. When I told one about making the team, he reacted like I had just told him that I was from outer space.

Professional conferences and workshop cruelly test your endurance in front of your peers (read: competition). For example, the annual meeting for Society for Neuroscience starts on a Saturday and runs through Wednesday. Talks start at 8 a.m. each day, and continue for 5 to 60 minutes, with more than a dozen ongoing sessions as any given time. Posters are presented in shifts, with hundreds simultaneously available for viewing. At 5 p.m., the at-conference bustle largely ends, but socials, meetings, lectures, and socializing (i.e., drinking) commence and continue into the morning hours. There are also several programs/events that precede or follow that main event. A couple of years ago, I spent a whole week at the SfN annual meeting in Washington, DC. It was so grueling that I skipped the last day of the conference in favor of spending the rainy day writing a manuscript and considered it a day "off."

We suck at communicating, but especially "thank you."
Everyone's been busy in the lab, using up the aliquot of this, the last of that, and spilling it on here. Sometimes, you fail to replace things or clean up after yourself before someone else also needs that resource. Both parties have the choice to be classy team players or unnecessary dickheads about the situation.

Dealing with equipment or facility issues can be a comedy of errors as each lab member independently discovers the issue or missing resource. A scientist could be royally screwed if they haven't accordingly planned ahead (which is probably most).

Periodically, the PI tries to show their appreciation for the lab team by providing food or drinks. It'd feel more meaningful if there was any real forethought, creativity, or commitment to it. Sure, they bought the food, but seldom is the act concurrently presented with an actual "thank you." It feels more like a tribute to an angry god than a team coming together to celebrate the group's efforts.

Team building and respect for one's peers is heavily undervalued and largely nonexistent.
Scientists, who appear to have a higher incidence of social awkwardness than the general population, work in groups that are hardly encouraged to communicate with one another. Without careful moderation, they won't actively challenge that difficulty. There needs to be a leader for or in the lab itself, aware of the social and functional culture of the lab. The chaos of every-awkward-(wo)man-for-themselves can easily devolve into shitty science work.

As a behavioral neuroscientist who works with operant chambers, I needed to quickly build up a competent crew of undergraduate assistants to help with the testing so that I could dedicate more time to the other things I need to learn, master, and accomplish as a postdoc. I solicited, interviewed, and trained an army of assistants with which I am excited to work everyday. It's a ton of front-end work and double checking that if implemented properly, pays major dividends in team member contributions. Because of them, I am frequently able to accomplish twice as much work as I would on my own and their efforts are a major factor in my scientific throughput. I get the feeling that my PI wouldn't agree with me, however, despite requisitioning my most senior assistant to take over a project dropped by someone under his own supervision.

Thinking is seldom considered to be productive, and haphazardly doing without thinking is generally promoted by the get-it-done-yesterday culture of science.
It wasn't until my fourth year of graduate student that an advisor demonstrated the importance of reading and thinking. It blew my mind! I had been focusing all my efforts on doing science with very little reading or understanding of science to guide it. Too few advisors and mentors encourage thinking about science in a creative way, especially when that time could be spent doing science.

I love having young science minds around me in the lab because I can't possibly espouse their worldview after 7 years of scientific devotion. Too few scientists solicit, or even value, the viewpoint or opinions of their fellow scientists. As a behavioral neuroscientist for seven years, I have developed firm opinions about how to get the best possible behavioral data out of my animals (obey their light cycles, avoid wearing or using perfumed products, approach animals with a calm, loving, but firm hand). Not that anyone would ask, however, so good luck with doing a cognitive task at the cusp of animals' day-night cycle while sporting that Axe body spray.

Likewise, my colleagues have strengths in techniques and fields that I don't know anything about. I wish asking for their help or opinion didn't feel so much like a confession of idiocy, even though it is completely normal and reasonable that I'm not the foremost expert in everything I do. Isn't having more smart people attacking a challenge better than fewer? Problem solving can be a funny thing - a novice could approach a problem with creative insight that a specialist in that field might not observe. Likewise, an expert might understand limitations with precision that can help modify a solution to fit the parameters at hand. Now that's fucking teamwork!



The only scientists you see working alone are in movies or TV, and they are generally "mad genious" scientists, and not in a good way (THERE'S AN ENTIRE WIKIPEDIA PAGE??!). I can think of villains  whose desire for fame, money, or power drove reasonable people to extreme ends. Sure - real science isn't a Hollywood movie, but it's also not completely unlike its depiction in films, either.

I firmly believe that while science is an academic endeavor, it is too seldom considered to be a group or team venture. I think failing to recognize and act upon this can make good, rigorous, and thoughtful scientific work more difficult to accomplish, and we already have enough barriers to that outside of what we scientists can directly control.




Thursday, May 23, 2013

If you liked it then you shoulda put your name on it

Dear everyone who's applied to or for anything ever:

Label the files that you email to someone in a way that would make the file names in someone else's possession make ONE MODICUM of sense.

For example, if you send me an email, and attach a resume(or CV), these file names make me want to reject you without further thought:

resume.doc
myresume.doc


This annoying little thing makes my frustrated mind over-value the resumes of people that actually put their name in the file. It's such a dumb little thing, but when there's a stack of applicants for a position, you might be surprised what people use as their selective criterion.



Like that one time, when someone forgot to spell check their email to me, and called me Dr. Swam.










... And then I stupidly and mockingly posted the above on Facebook, and now some of my roller derby family (lovingly?) call me Dr. Swam or Swammy.


So... yeah. Label those files.


Tuesday, May 21, 2013

I'm such a fool for you

Because of my need of organization, I have now accepted that I will forever be in charge of cleaning and putting things away - both at home and in the lab.

FML.

Now, I'm not saying that my lab mates are filthy pigs - in fact, I have a great lab family and I really like them. It's just... that there's a pervasive culture of not putting things away. In my experience, the outlook is poor for getting people to put their lab equipment away after it's been cleaned and dried. That minuscule area by the sink is constantly brimming with tools to be autoclaved or put away. It's literally limbo for lab tools.

Once a week, I've now resigned myself to putting things away. Sometimes I need to, because it's the only way I can place my used tools there to dry. Sometimes I'd prefer to postpone whatever science I have slated for the day in favor of the mindless indulgence that is organizing. Sometimes I do it because I have undergraduate assistants around me almost all of the time, and they need to be taught how to be good lab citizens.

There's absolutely nothing harder than trying to get a lab member to change a bad lab citizen habit. It's easiest to pretend it never happens, and hope that you can eventually have more good than bad lab mates. Maybe you can approach a poor citizen individually, and appeal for considerate behavior. ...And sometimes you let it roll, suck it up, and clean up after them silently. Not all lab mates are perfect or permanent, and sometimes it's easier to simply wait for the ticking time bomb to explode (or graduate, because that happens sometimes).

So today, I raise my glass to my lab mates. I put away your shit like a bitch.

Monday, May 13, 2013

Lies and Recomendations

I wish I could have an honest conversation with a professor who's written at least 20 recommendation letters. Maybe 50? ....100?

Wait, how many letters will a professor write in their time? That got scary fast.

Whilst attempting entrance to graduate school, I had a letter writer fail to send promised letters. I apparently wasted time completing tedious applications and a boatload of money during my college-induced poverty because some dickhead lied to my face. The part that made it so excruciating was that he was not the only asshole liar to exploit my work in academia. I'd spent my junior year of college managing research assistants and collecting human-subjects data for that asshole's graduate student. His student absconded with the data to a post-doctoral position in Texas somewhere and never again responded to correspondence. Upon hearing the issue, his advisor agreed to write letters in his stead. Note: agreed to. NEVER ACTUALLY DID.

Now, in full disclosure, I am *JAZZED* that things turned out the way they did. Apparently so glad that I have completely forgotten the name of the graduate student who was the ultimate culprit in the above debacle. During my senior year I worked in a lab with amazing researchers (Gerald Wasserman, Mandy Bolbecker-Hosking). I later joined Mike Hoane's lab at Southern Illinois Unviersity as a graduate student and fell in love with traumatic brain injury work in the following application cycle. Met my future husband, fell in love roller derby culture with some people in Southern Illinois, blah, blah, blah. Birds singing, sun shining, everything is perfect and wonderful.

...Yet there's still a little salt in my soul about that damned letter.

I needed a crew of assistants to help with operant chamber testing, and that's now ballooned out to more than a dozen assistants. Most people balk at the number assistants, but these rad miniscientists substantially increase the quality and throughput of my research. There's a time trade-off for me - management, recruitment, retention, and enrichment requires substantial effort, but it's VERY worth it, in my opinion. 

My recommendation letter guidelines:
1. I honestly assess their letters' potential content to the apprentice (while working together or when asked for a letter, but preferably the former).
2. Apprentices provide as much notice as possible, with a plan in place, ao I can easily complete the letter and send it.
3. I supply a copy of the letter to the apprentice following its submission.

It's my belief that if you're going to train or be trained someone, there is ideally a commitment to doing so well. It would be easier for one to know how they could excel if the rubric on which they will be graded is clearly described. Mandated for courses, unheard of with research assistantships.

As the discipline of Neuroscience matures and becomes a recognized and established independent academic entity, I'm excited to see how the recommendation letter evolves. Research involvement whilst and undergraduate is an increasingly necessary component to admittance to Neuroscience graduate programs (as well as many others). Maybe the recommendation letter culture can sustain a similar evolution.

At least it's digital now. Letterhead is a bitch.

Thursday, April 25, 2013

Like a Boss

About two years ago I had sushi with a mentor, shortly after I finished my PhD and was preparing to set up operant chambers for mice in a fledgling lab. She told me to get undergraduate assistants IMMEDIATELY.

"But I don't even know what I'm doing, yet. I've never run or programmed systems like those" I balked.

She wove me off, dismissively. "Trust me."


Spoiler Alert: She was absolutely right. I now have 16 assistants.


Here are some things that I have learned in the five semesters during which I have accepted undergraduate assistants:

First and foremost:
Be pro-choice. Be the master of your own destiny and select your own assistant(s). Sure, entertain others' opinions, especially if your boss wants to contribute to this decision, but be clear that your thoughts matter. This is someone in whom you're probably going to invest a lot of time and effort. This person might someday be a representative of your lab, training, or institution. You want to do your best to ensure that that goes over well.

Applications and Interviews
1. Planned graduation date matters. I view a one-year commitment as the minimum any assistant should expect to invest in a worthwhile research endeavor. Better yet, anyone who spends even more time with one lab is more likely to develop independent skills, run an independent project, or just become familiar with scientific culture.
2. Motivation influences effort and even type of lab involvement. Whether a student plans on making application to medical/dental/pharmacy school or graduate school can be a major indicator of what approach they will take to their research assistantship. More of my graduate-school aspiring students are interested in running their own study than my m/d/p-school aspiring students. 
3. Informal interview. Would this person get along with the other personalities in the lab? Did this person do any 'homework' before coming in to talk about also working on our science? What kind of person or team member would they be like?

Training
1. Train once, check twice, and repeat until their efforts are satisfactory. Poor performance by a student can be attributable to poor training and guidance, too. Don't forget that.
2. Paperwork sucks but creating an easy guide/tracking/system to knocking it all out is key.

Involvement
1. Say please and thank you. A lot. 
2. Be reasonable. Things happen, people get sick, life falls apart, people mess up. I'd rather that none of that stuff affects any of my work, but when it inevitably and reliably does, I roll with the punches. Healthy, happy, relatively-relaxed and secure assistants make better learners and team members. Only get uptight about these things if a worrisome pattern emerges, and then deal with it head-on.
3.Establish regular, clear, and frequent communication with each of them individually.
4. Make time to sit down with each assistant individually, about once a semester, to examine goals, situation, plans, and whatnot. It goes a REALLY long way.
5. Keep your PI in the loop. Better yet, try and make them part of it, if time permits*.



I invest a substantial amount of time ensuring that this working relationship is meaningful and functional for both parties. I think that's made very competent, happy, dedicated assistants that I can count on for semesters to come. This semester, I graduate the first of my amazing assistants, and I have to admit that I do feel a little bit proud for them. The last year felt a bit like watching grow up, at least in science.

And like them, I try to be constantly learning about what I can do to become a better scientist, mentor, and supervisor. You know, like a boss.

*realistically, LOL