Wow! This is *such* a big topic. Although it's impossible to squeeze two semesters of classwork into an hour, I could definitely speak on it, but I'd have to keep it on "just the basics"... I'd also drag one of my peers from work in to do this talk (he has a degree both in Microbiology and in Computer Science and can field a lot of the questions).... <div>
<br></div><div>We could do a tech talk which answered just the self-evaluation questions I sent in a recent email and did some very basic BioPython and webqueries. I know BioPython has fallen out of favor in the past few years, but it's great for doing things like iterating through FASTA sequences, getting sequence lengths, converting from one sequence format to another, etc. And, it's very simple to use - which makes it a great fundamental tool for a basic tech talk. I saw at least two people who were much more qualified than I was on this list - I'd happily speak with them. My topics, however, would assume the audience has zero Biological background.</div>
<div><br></div><div>If there's an interest, I could certainly try to put something together. I guess the fundamental question is, how many people would really be interested? Especially since this is 95% basic science and the programming is dead simple (iterating through a sequence and getting some results). We don't have the science to do more complex programming examples.</div>
<div><br></div><div>We could also do a basic demo of Pymol too - but that would be showing pretty 3D models of molecules (proteins in our case) using a tool that's already created.</div><div><br></div><div>I could do this starting January -- but again, I'm not certain how interested our entire group would be since it's heavy on the science you need to understand as background and very light on the actual python/programming.</div>
<div><br></div><div><br></div><div>Cheers,</div><div><br></div><div><br></div><div>Glen</div><div>P.S. Feel free to comment off list to me if this is something that doesn't have to be said publicly.</div><div><br></div>
<div><br><div class="gmail_quote">On Sat, Oct 10, 2009 at 10:19 AM, jim <span dir="ltr"><<a href="mailto:jim@well.com">jim@well.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
is there a BayPIGgies talk in this?<br>
generally the issue seems to be bringing<br>
application-specific experience to programming<br>
skills. more specifically, biology and medicine<br>
application areas and python--this growth area<br>
includes non-intrusive hardware solutions.<br>
<div class="im"><br>
<br>
<br>
On Mon, 2009-10-05 at 18:36 -0700, Glen Jarvis wrote:<br>
</div><div><div></div><div class="h5">> My team is looking for another programmer (yeah!)<br>
><br>
><br>
> But, I must tell you, finding a fit for us here will be very<br>
> difficult. You need to know Bioinformatics well enough to be able to<br>
> to understand the directions given (a challenge for everyone when they<br>
> start here -- even PhDs in this field).<br>
><br>
><br>
> So, here are some basic questions to help you sort out, "should I even<br>
> read on?"<br>
><br>
><br>
> * Do you know the difference between DNA and Amino Acids? (Bonus if<br>
> you have all the Amino Acids memorized -- I still don't)?<br>
> * Do you know what is a gene (i.e., how is a gene different, if it is,<br>
> than a bunch of amino acids strung together as residues)?<br>
> * Do you know what a phylogenetic or phylogenomic tree is?<br>
> * Do you know what I mean by a predicted 'active site' in a molecule?<br>
> * Can you describe the shape of an amino acid (i.e., when formed<br>
> and/or when in an environment conducive to folding)<br>
> * Do you know what Biopython is and why it is useful?<br>
> * Do you know what a neighbor joining tree is? (Or Maximum Likelihood<br>
> Tree, Maximum Parsimony Tree, Quick Tree, etc.)<br>
> * Do you know what a Pairwise Alignment is and how it differs from a<br>
> Multiple Sequence Alignment (MSA)<br>
> * Do you know how to lookup an accession number in Genbank? (Or<br>
> Switprot? Or Pfam?)<br>
><br>
><br>
> These are basic 101 questions, FYI. You should know a lot more, like<br>
> what a Baysean network and Hidden Markov Models are. You don't have to<br>
> know every single thing listed above, but if it's all completely alien<br>
> to you, you *will* be in for a struggle -- especially if you don't<br>
> know Python/Django that well.<br>
><br>
><br>
> What would work in our team, you may ask? Someone incredibly<br>
> proactive and who won't be intimidated easily. For example, if a PhD<br>
> told you they needed something to happen, described it graphically<br>
> (what it should look like), but not understand any of the difficulties<br>
> (like databases, javascript, html, etc.) to make that happen, would<br>
> you get frustrated, or would you make a plan on your own and make that<br>
> happen? How could you deal with the frustration if the PhD didn't<br>
> understand what was taking so long because they're focused on the<br>
> result instead of infrastructure, how would you address this<br>
> proactively?<br>
><br>
><br>
> Can you read incredibly messy old HTML, JavaScript and Perl code, but<br>
> write incredibly pristine python/django/jquery code, and do it<br>
> quickly? That is, can you write code that JJ would give a thumb's up<br>
> too, and write it quickly? [JJ isn't involved in this job, I just use<br>
> his high standards as my internal barometer in my own code. I've not<br>
> yet written code that JJ hasn't found a problem with (good for me -<br>
> I'm learning every time he does a code review with me).]<br>
><br>
><br>
> Are you willing to take an incredibly low salary (comparatively)<br>
> because you're that interested in science, working for an very well<br>
> known research facility, etc?<br>
><br>
><br>
> I'm not asking the impossible - I fit the criteria above and will be<br>
> working along side you (as well as one other). I struggle with some of<br>
> these things a lot too. There are times it feels like a Dilbert<br>
> cartoon here -- but, at the end of the day, we're doing some pretty<br>
> awesome things. You'll get frustrated at the old system and how bad it<br>
> is (PHP writing HTML writing JavaScript writing HTML (Forms) writing<br>
> more JavaScript writing lord-knows-what at times). You won't be able<br>
> to pull on all the old threads (somethings can't yet be changed for<br>
> fear of damaging processes no one knows about).<br>
><br>
><br>
> We're building a new system that mimics the functionality of the old<br>
> system - but clean and organized and well tuned. You'll be doing<br>
> Python and Django, but will probably also need to know a good deal of<br>
> HTML, JavaScript, JQuery, etc in the web stack. (I don't know<br>
> JavaScript and JQuery that well, but I'm working on it). Also, the new<br>
> system is, thus far, organized/clean/and a joy to create.<br>
><br>
><br>
> It's tough to find someone who's a good fit -- and willing to do this.<br>
> But, if you're looking and want to talk to me about it, I can help you<br>
> figure out if this is a position you may be interested in or not. I<br>
> mean, heck, you got this far, didn't ya :)<br>
><br>
><br>
> I'm not a recruiter -- just looking for a python peer who would be<br>
> excellent to work with.<br>
><br>
><br>
><br>
><br>
> Cheers,<br>
><br>
><br>
><br>
><br>
> Glen<br>
</div></div><div><div></div><div class="h5">> _______________________________________________<br>
> Baypiggies mailing list<br>
> <a href="mailto:Baypiggies@python.org">Baypiggies@python.org</a><br>
> To change your subscription options or unsubscribe:<br>
> <a href="http://mail.python.org/mailman/listinfo/baypiggies" target="_blank">http://mail.python.org/mailman/listinfo/baypiggies</a><br>
<br>
</div></div></blockquote></div><br></div>