I Hate Coding

It all started in 6.00. I actually liked that class at first. When the p-sets would come out the week before they were due, I would stay up until 5am doing them. They felt like puzzles, and it was fun because they were pretty simple to code and because it was all about thinking algorithmically. I believe that the longest it took me to run any program was five minutes tops.

And then I took 15.053 and had to learn Julia. The only frustrating thing about Julia is that there aren't a lot of online tools to help you debug the code. So on a night of two problem sets due the next day, I had spent an hour debugging my simple code only to find that I had a space where there shouldn't be one. A whole hour... for a space... I was frustrated and angry because it was such a little thing. Whatever, I moved on.


And then 20.109 comes along and says, "Let's use R!"

M2D3: grrr... fine...

M2D4: hey, this actually works kinda!

M2D5: So, um, the TAs say they don't know what I did to the computer. I think I just broke R.

Getting everything done for Benchling:
Okay, so I just have to download these packages, and I'll be all set.                                                        *10 min later*
package not found: huh, that's weird... Internet, help me!
*gets packages installed*
okay, now I can just run the code we wrote in class.
*15 minutes in*
DESeq2 not found: seriously? okay, back to the internet.
*think I've fixed the problem*
DESeq2 not found: but, but, you just told me it was installed!

So that basically goes on for a while... And then with some help from Christina, it finally works and I have my Benchling ready on time.

A couple days later, I decide to get started on the research article. I start trying to do the figures for the results section and realize that I want to run some more R to get another figure for my article.
And there it was, the dreaded... "DESeq2 not found"

 And all of a sudden, that one little package screws everything up, and it's snowballing and snowballing as more problems keep popping up. Like, I swear it worked a few days ago!


I know I'll end up coding again and find it extremely useful, but I also know that it's always just going to be so frustrating... Running time, tiny bugs that aren't obvious, working one day and then not working the next...
It's all complicated. I think I finally understand how everyone else felt in math class growing up.

Comments

Post a Comment

Popular posts from this blog

The Power of Statistics

Image
“Aaaaaah…..” “Oh, no!” (returning off the aspirator) “I’m sorry.” “What do we do?” (squeezing the aspirator tube) “Can we break the vacuum?” “Let’s pull together.” (pulling on the aspirator tube in two opposite directions unsuccessfully…) On the third day of Mod 1, my partner and I aspirated our +IPTG induced pellet. I was so convinced that we should aspirate the left over supernatant with an aspirator because it worked well for the –IPTG control pellet. Why did an n=1 experiment convince me that aspirating would be safe?  Consider a hypothetical situation where before any experimentation, I think there’s a 1/2 probability that the aspirator cannot aspirate a pellet, and 1/2 probability that aspirator can aspirate a pellet and does it half of the time. One successful aspiration should only increase the probability that the aspirator cannot aspirate a pellet to P conditional = 0.5/(0.5+0.25) = 2/3. So a successful aspiration should increase my confidence in aspiration
Read more

Seeing the finish line!

The research proposal assignment start out as fairly intimidating.  Since 20.109 is my first introduction to biological engineering, I've appreciated being told exactly what to do.  To be tasked with crafting a research project that solves a biological problem, is original, and creative sounded like a lofty goal.  However, the more papers I read, the more I realized the real challenge was not having to come up with one idea, is was having too many ideas/options.  Even after Masrur and I had decided upon a pathway to target, there are so many diseases that the pathway is involved in that we then had to choose the most compelling disease to focus on.  Since we spent so much time deciding upon what exactly we were studying, we left little time for ourselves to define the research aim and detail the methods.  Overall, though, the project was really interesting and engaging.  I even found myself disappointed that the proposal wasn't real and that I wouldn't actually be able to o
Read more

Don’t judge a module by first sight!

Different from Module 1 and Module 2, Module 3 is less molecular biology focused and not directly related to medicine. At the beginning of Module 3, I thought that I would enjoy this module less as it seemed less relevant to my primary interest in medicine and cancer research. However, I was wrong. I truly enjoyed this module, from TEM to making batteries, from brainstorming research ideas to presenting our research proposal. It was my second time seeing TEM samples, but it was just as fascinating as the first time. The phage nanowires were intertwined with evenly distributed gold nanoparticles, and the gold atomic planes were so regular and amazingly beautiful. On the last day of Module 3, it was so exciting to see batteries being made, and to light up LEDs using batteries with the cathodes we made! The unimaginable beauty in the order, simplicity, and complexity of nature, from atoms to nanoparticles, from proteins to cells to organisms, is what drew me to biology in the
Read more