Seqanswers Leaderboard Ad

Collapse

Announcement

Collapse
No announcement yet.
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Joann
    replied
    Me too

    Would like to weigh in on the side of rskr. As a biologist employed by hard core computer scientists, they do their thing and I do mine to complete our deliverables. True, we mostly find each other's science mostly boring and I admit I am not even motivated to learn Linnux or shell scripting or much else that would contribute to making me a practicing bioinformaticist. I strongly believe biology totally needs core computational scientists as allies to provide us their perspectives and facilitations to add to and progress our own field. Sometimes the realizations I arrive at here about biological scientists are shameful= we do not yet have a global, uniform and systematic way to name new genes and to mention practicing the use of a gene ID number over some letter symbol is talking to the wall, for example.

    Leave a comment:


  • rskr
    replied
    Originally posted by ETHANol View Post
    Why must you be such a troll.

    Normally, I would ignore such blatant trolling but being a confused molecular biologist not so long ago I thought it was important for this guy to understand what we are dealing with here, i.e. trolling and not useful information.

    rskr, I'm done you win. All interpreted languages are without merit and you cannot be a good scientist if you use them. People that program in C++ are superior.
    I gave my "opinion", which has been attacked by people who can't tell an integer from a char, and obviously have some stake in having people believe certain ways about certain languages, these languages which they do not even know. For example that "C has a very long development time"(it probably does if you don't know it in the first place. Or that "C++ programmers aren't interested in biology". etc. Or that "C++ is poor career choice." Or "I believe the interpreted languages are without merit", I said lack of merit, not without merit. I use interpreted languages, however there are many a program which I wish were written in C++ instead, a prime example are the AMOS tools that didn't scale to high-throughput sequencing. If the programs had been written in C++ they would have been better.

    So I would like an apology if you have the time, since many of the things you said were not true and offensive to me.

    Leave a comment:


  • ETHANol
    replied
    Why must you be such a troll.

    Normally, I would ignore such blatant trolling but being a confused molecular biologist not so long ago I thought it was important for this guy to understand what we are dealing with here, i.e. trolling and not useful information.

    rskr, I'm done you win. All interpreted languages are without merit and you cannot be a good scientist if you use them. People that program in C++ are superior.

    Leave a comment:


  • rskr
    replied
    Originally posted by ETHANol View Post
    That's it you think it is all about the program and never about the biology. Wake up and realize that a lot of people have other interests then you, which can be better served by learning one of these languages you despise so much. I am a wet lab scientist, I would be a total wast of my time to learn C++, while some Unix, Perl and R are extremely useful.
    Well, go study something else then, and quit whining about the realities PERL's lack of merit.

    Leave a comment:


  • ETHANol
    replied
    That's it you think it is all about the program and never about the biology. Wake up and realize that a lot of people have other interests then you, which can be better served by learning one of these languages you despise so much. I am a wet lab scientist, I would be a total wast of my time to learn C++, while some Unix, Perl and R are extremely useful.

    Leave a comment:


  • rskr
    replied
    Originally posted by ETHANol View Post
    How many Cell, Science and Nature papers have been published using reused Perl scripts and Bioconductor packages? Has that all been a waste of time?
    I don't have a problem with it. I just wouldn't consider the Perl scripts "forward thinking" compared to the program or programs that were used by the Perl scripts. It takes quite a bit of forethought to write a program that many people can use for many different purposes, and not much forethought to use these programs.

    Leave a comment:


  • ETHANol
    replied
    Rskr, you are into pushing the state-of-the-art on the computing side. Some people are much more interested in the biology and find the computing side really boring. There is limited time in life and limited brain space (maybe not yours). So a lot of us learn what we have to to answer the biological question we are interested in.

    I could go to a hot-spring and find a bug with a more efficient polymerase for PCR or I could just use one that is currently available to do interesting research. Some people have made their life's work the former, many more have focused on the latter. Some people learn C++ and come up with better algorithms some use the existing ones and write perl scripts to do interesting research. Why do you have a problem with that? How many Cell, Science and Nature papers have been published using reused Perl scripts and Bioconductor packages? Has that all been a waste of time?

    Leave a comment:


  • rskr
    replied
    Originally posted by ETHANol View Post
    Here is some advice, anyone that says language xxxx is garbage and a waste of your time is blind (unless you are talking about some language of yesteryear).

    Rskr, you ask, why piece together a bunch of algorithms that someone else wrote that are totally sufficient to answer the biological question you are addressing when you can make your own? Because it saves a lot of time, you'll publish your project sooner, which usually means in a higher impact journal, which means better career options.

    We could blow our own pipets in the lab from glass, but that wouldn't make us better scientists.
    Sometimes the pieced together programs are sufficient to answer the question, other times people don't understand what is in the program well enough to say one way or another(but that doesn't stop them). To that end even if one does not become very proficient in C it will give them an advantage over those who don't. Sometimes there is a missing piece or your perl program isn't fast enough to analyze modern high-throughput experiments, what do you do then? Its been my experience that these experience perl programmers have already figured out everything you can do with canned programs, so good luck publishing something that hasn't been done by taking output from program A and putting it into program B.

    Leave a comment:


  • ETHANol
    replied
    Here is some advice, anyone that says language xxxx is garbage and a waste of your time is blind (unless you are talking about some language of yesteryear).

    Rskr, you ask, why piece together a bunch of algorithms that someone else wrote that are totally sufficient to answer the biological question you are addressing when you can make your own? Because it saves a lot of time, you'll publish your project sooner, which usually means in a higher impact journal, which means better career options.

    We could blow our own pipets in the lab from glass, but that wouldn't make us better scientists.

    Leave a comment:


  • rskr
    replied
    Originally posted by ETHANol View Post
    rskr does not understand
    Sorry, I thought he was interested in "Forward looking" learning, not quick and dirty piece together a bunch algorithms someone else wrote, without much justification or understanding. I assure you, you don't need to learn much to do the latter, wait until the time comes.

    Leave a comment:


  • ETHANol
    replied
    rskr does not understand that there are a lot of biologists that are more interested in biological questions then hard core computer science. He likes to try to diminish anyone and any work that uses an interpreted language. He has a lot of work ahead of him. We use the tools that allow us to answer our questions with the least work.

    This is the path I would suggest:
    1. You will not learn anything unless you are actively and currently using it for something. So come up with a project you will use this stuff.
    2. Learn some Unix
    3. Learn some Python and/or Perl (Python is structured more like R so it can help with the next step, but I know Perl better).
    4. Learn some R.
    5. Keep working on what interests you.

    If after all this you decide you want to mostly give up molecular biology and become a hard core computer scientist, then you can move onto C++.

    Great place to start:

    Leave a comment:


  • Mark
    replied
    To rskr's point, yes C is a good choice if you plan on doing a lot of fundemental algorithm development or are at a point in in your life where you are interested in programming from a mostly academic perspective and wouldn't be hampered by it's (or Java's) longer development times. If on the other hand you need to be quickly productive and are mostly interested in piecing together and interpreting NGS and other high-throughput data using the vast amount of open source analytic programs available, I believe (having worked in industrial bioinformatics for years) you would be much better off with Perl (my favorite) or Python, neither of which are fads.

    Leave a comment:


  • steven
    replied
    Originally posted by dpryan View Post
    My 2 cents:
    • The Unix CLI: This includes common commands such as awk, sed, and cut. I would also include shell scripting in this. This bullet point is required to put together any sort of basic analysis pipeline.

    • R: Inevitably, you end up needing to crunch number in R, so go ahead and get at least a passing familiarity with it. This may include various bioconductor packages, depending on what you're doing

    • Python or Perl: It doesn't really matter which one. You can do pretty much anything in these languages, though they have their limitations.

    • C/C++/Java: If you get to the point of writing more "heavy duty" programs that require any significant performance then you'll need one of these. You would generally learn one of these last.


    It's probably best to learn things in that order, possibly swapping the order of R and Python/Perl.
    +1
    Totally agree - and swapping Python/Perl before R

    Leave a comment:


  • rskr
    replied
    In a forward looking manner I wouldn't bother with Perl/Python/Java they are mostly just fads and any location you might want to work is just as likely to use the one you don't know, for no other reason than the CEO liked the monty python jokes or coffee. These scripting languages are easy enough to pick up if you know how to program in C, and most cool molecular dynamics simulators are in C for obvious performance reasons. Unix command line utilities are very handy for getting things done, and PERL and Python both draw heavily on the conventions so if you encounter a script done in either of these you should be able to figure out what it does(knowing linux that is).

    Leave a comment:


  • dpryan
    replied
    My 2 cents:
    • The Unix CLI: This includes common commands such as awk, sed, and cut. I would also include shell scripting in this. This bullet point is required to put together any sort of basic analysis pipeline.

    • R: Inevitably, you end up needing to crunch number in R, so go ahead and get at least a passing familiarity with it. This may include various bioconductor packages, depending on what you're doing

    • Python or Perl: It doesn't really matter which one. You can do pretty much anything in these languages, though they have their limitations.

    • C/C++/Java: If you get to the point of writing more "heavy duty" programs that require any significant performance then you'll need one of these. You would generally learn one of these last.


    It's probably best to learn things in that order, possibly swapping the order of R and Python/Perl.

    Leave a comment:

Latest Articles

Collapse

  • seqadmin
    Strategies for Sequencing Challenging Samples
    by seqadmin


    Despite advancements in sequencing platforms and related sample preparation technologies, certain sample types continue to present significant challenges that can compromise sequencing results. Pedro Echave, Senior Manager of the Global Business Segment at Revvity, explained that the success of a sequencing experiment ultimately depends on the amount and integrity of the nucleic acid template (RNA or DNA) obtained from a sample. “The better the quality of the nucleic acid isolated...
    03-22-2024, 06:39 AM
  • seqadmin
    Techniques and Challenges in Conservation Genomics
    by seqadmin



    The field of conservation genomics centers on applying genomics technologies in support of conservation efforts and the preservation of biodiversity. This article features interviews with two researchers who showcase their innovative work and highlight the current state and future of conservation genomics.

    Avian Conservation
    Matthew DeSaix, a recent doctoral graduate from Kristen Ruegg’s lab at The University of Colorado, shared that most of his research...
    03-08-2024, 10:41 AM

ad_right_rmr

Collapse

News

Collapse

Topics Statistics Last Post
Started by seqadmin, 03-27-2024, 06:37 PM
0 responses
13 views
0 likes
Last Post seqadmin  
Started by seqadmin, 03-27-2024, 06:07 PM
0 responses
11 views
0 likes
Last Post seqadmin  
Started by seqadmin, 03-22-2024, 10:03 AM
0 responses
53 views
0 likes
Last Post seqadmin  
Started by seqadmin, 03-21-2024, 07:32 AM
0 responses
69 views
0 likes
Last Post seqadmin  
Working...
X