Adviser Meeting

I've come to realize a few things about my adviser since I met him back in Spring 08.

• He's a night owl. This man has a schedule that is approximately 7-8 hours behind everyone elses. He would need a night job if he was not an intellectual.
• He's a procrastinator. Papers and proposals get put off until the last minute. And, as my dad would say, at the last minute, he makes sure it really is the last minute. If it isn't, resume procrastination.
  
• He has idyllic visions for our research together. He believes that I can get the majority of the work needed for my dissertation done by May.
• He shifts from optimism to pessimism at the drop of a pin. Paper writing has been particularly manic as he decides the paper is amazing/crap from day to day.
• He is not my style. I would rather work with someone who is a "planner." I'd rather have things ready to go ahead of time than barely on time.

At my meeting, we talked about the following things: explaining our contributions better, mapping a yeast library, future papers, module locking, indicator molecules, classifying what we know, implementing other functions in verilog, parsing, web interfaces, Chad & Megan (whom I've never met), level sensitivity and consuming, upcoming conferences, stochastic modules, experimental labs, research brochures, and BICB people.

The notes I scribbled in my notebook are essentially that list. I gathered that he wants me to do... research... about stuff... and write papers... and be a general wreck for another three months...

I've got a lot on my plate for the upcoming semester... and I actually need to pass/finish my classes this time. Keeping a 3.3GPA in grad school is going to be harder than I thought.

If I have the chance, I'm going to write an overview of my research as a series of blog posts this week. It might help me in the long run. Hopefully I can explain it properly.