2. Parallel sequencing lives, or what makes large sequencing projects successful https://academic.oup.com/gigascience/article/6/11/gix100/4557140?login=false

3. Common-sense approaches to sharing tabular data alongside publication https://www.sciencedirect.com/science/article/pii/S2666389921002300

4. A Reproducible Data Analysis Workflow with R Markdown, Git, Make, and Docker https://psyarxiv.com/8xzqy/

5. Practical Computational Reproducibility in the Life Sciences https://www.cell.com/cell-systems/fulltext/S2405-4712(18)30140-6

6. A video by Dr.Keith A. Baggerly from MD Anderson [The Importance of Reproducible Research in High-Throughput Biology](https://www.youtube.com/watch?v=7gYIs7uYbMo) highly recommended.

7. Ten Simple Rules for Reproducible Computational Research http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1003285)

8. Good Enough Practices in Scientific Computing http://arxiv.org/abs/1609.00037 

9. Best Practices for Scientific Computing https://journals.plos.org/plosbiology/article?id=10.1371/journal.pbio.1001745

10. A Quick Guide to Organizing Computational Biology Projects http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.100042  A must read for computational biologists!

11. Reproducibility of computational workflows is automated using continuous analysis https://www.nature.com/articles/nbt.3780

12. Five selfish reasons to work reproducibly https://genomebiology.biomedcentral.com/articles/10.1186/s13059-015-0850-7

Reference: http://www.unitedformedicalresearch.com/wp-content/uploads/2013/06/The-Impact-of-Genomics-on-the-US-Economy.pdf

https://labs.utsouthwestern.edu/bioinformatics-lab/positions

1. Learn and get updated

Some of the bad biological programmers only learn new technical or non-technical things when it’s absolutely necessary. The good biological programmers learn new technical skills proactively. But great biological programmers not only learn new technical skills on their own but also learn non-technical skills, and have an open mind to sources of knowledge that others may shut out.

In other concrete term, the bad biological programmer learn Perl's regular expression when they started a project on comparative genomics; the good biological programmer learned it a year before because it looked interesting; and the great biological programmer also read about the BioPerl packages, genomics, DNA string, genomic theories, or some similar course of study so that they could understand the results and explain it biologically.

2. Not a merely coder!!!

I often encountered with biological programmer who call themself a hard-core computer programmer and avoid biology. I can almost guarantee that if you are one of them then you are not doing research but merely writing "dry" codes.

According to my supervisor most of the computational biologist, don't know what they are doing biologically. Even they struggle to explain their own programs output and results. Therefore, It is highly advisable to learn basic of biology which can assist you to explain the result and understand your discovery. Always remember you are a researcher not a coder.

3. Be Social with biologist

The computational biologist spends most of the time in from of computers, writing codes. They always think their job is to produce working codes, not technical research perfections. But, they are completely wrong. You should not forget that apart from your computational skills you also need some biologist, other than your supervisor, to explain and make you understand the complex biological mechanism.

I highly recommend your to interact with biotech researchers and learn how do they explain their one graph (which they generally produce after one year of work) biologically. Remember, the origin of your research project is complex biological phenomenon, which is more complex than that of your limited programming rules.

4. Do not search, research for answers

Researching for answers means more than typing several keywords into a search engine or posting a question at Stack Overflow or the BioStars forums. I have entered problems into search engines that generate no results, and every question I posted on Stack Overflow or the BioStars forums never got anything resembling an answer, yet I solved the issues and moved on. I’m not a magician — I just know how to find answers or discover root causes.

Many problems are situational, and if you depend on search engines and forums, you can waste a lot of time going down a rabbit hole and possibly never getting a solution. Learn to perform root cause analysis, learn enough about the underlying system to look for other clues and solutions, and learn to take a long distance view of an issue before deep diving into it.

5. Love and defend your research

You cannot rise to the top in this research profession without loving your work. There are some very good “it’s just a job” biological programmers (I’ve been one at times), but if that is your outlook, you won’t be willing to do whatever it takes to succeed. This idea gets a lot of folks in a huff, because they feel it is a personal insult. “I’m a good programmer, but I have other priorities and can’t make work my life.” I understand completely; I have other priorities too. As much as I hate to say it, when I am passionate about my work, I am willing (though not eager) to abandon my other priorities to finish the job. It is not an insult to say that if you aren’t willing to pull out all the stops you can’t be the best, it is a fact.

You must be passionate about more than programming — you must also be excited about your research, the tools and technology you are using, and so on. I have seen very good and even great biological programmers operating at mediocre levels because something was not a good fit, such as they hated the project or were using a technology they disliked. Therefore, like your research project and get excited about your discoveries. You have not only to discover but also defend your finding with scientific words.

Thanks to all of you for reading.

https://evomics.org/2024-workshop-on-genomics/

Address of the bookmark: https://evomics.org/2024-workshop-on-genomics/

MEME Suite software development; gene expression; mathematical modelling; gene regulation and transcription

Specialization:
Pattern recognition and modelling in computational biology

Link @ http://www.imb.uq.edu.au/tim-bailey

About the person:

Essential criteria:

Hold or be about to obtain* a PhD in Computational biology, Bioinformatics, computing science or related subjects. (*must be obtained within 3 months of the closing date for the post) or MSc equivalent with at least 3 years' work experience in a relevant role.
Significant relevant research experience in genomics or work experience in a relevant technical/scientific role.
Significant experience in managing and analysing NGS data and other big data.
Experience in developing and maintaining analysis pipelines.
Experience working with Linux/UNIX environments.
Proficiency with python, bash, R and/or equivalent languages.
To be successful at shortlisting stage, please ensure you clearly evidence in your application how you meet the essential and, where applicable, desirable criteria listed in the Candidate Information document linked on our website.

More at https://hrwebapp.qub.ac.uk/tlive_webrecruitment/wrd/run/ETREC107GF.open

Link @ http://www.newcastle.edu.au/research-and-innovation/centre/cibm/about-us

We are looking for a highly motivated candidate with a PhD degree in
Bioinformatics or a related field. Candidates are expected to have a
strong background in evolutionary biology and/or comparative functional
genomics. Additional experiences in single cell functional genomics
analyses, statistics and computational data analyses are a plus, as is
an interest in comparative developmental (EvoDevo) questions.

We offer a dynamic and interactive research environment with state-of-the
art research facilities, good research funding and internationally
competitive salaries.

The Tschopp lab (www.evolution.unibas.ch/tschopp/research/)
studies the gene regulatory mechanisms of cell type
specification and evolution in vertebrates. See also our
preprints at https://doi.org/10.1101/2024.03.26.586769 and
https://doi.org/10.1101/2024.11.28.625862 Applications should include
a motivation letter, a CV, a list of publications, a statement about
research interests, as well as the names and contact details of at
least two referees. Applications (in the form of a single .pdf file)
should be sent to Patrick Tschopp (patrick.tschopp@unibas.ch); review
of applications will begin on January 1st 2025, and will continue until
the position is filled.

Patrick Tschopp

Classes for
Multiple alignment (Bio::Alignment),
Gene Ontology(Bio::GO),
PDB (Bio::PDB),
FANTOM database(Bio::FANTOM),
GFF (Bio::GFF) and KEGG
Orthology (Bio::KEGG::KO).

They also added support for many applications such as PSORT, SOSUI, TargetP, TMHMM, GenScan, ClustalW, MAFFT, and KEGG API.

Wiki Links
http://bioruby.open-bio.org/wiki/BioRubyOnRails
http://dev.bioruby.org/en/

BioRuby in Anger
http://dev.bioruby.org/en/?BioRuby+in+Anger

BioRuby RDocs
http://bioruby.org/rdoc/

BioRuby Tutorial Website
http://dev.bioruby.org/en/?Tutorial.rd

Why BioRuby Hub for BioRuby
http://www.linuxjournal.com/article/5915

Social Coding Hub for BioRuby
http://www.linuxjournal.com/article/5915

Bioinformatics on Rails: BioRuby Tutorial
http://bioinforuby.blogspot.com/2008/02/bioruby-tutorial.html

RRA BioRuby
http://raa.ruby-lang.org/project/bioruby/

BioRuby Project Discussion Group
http://portal.open-bio.org/mailman/listinfo/bioruby

BioRuby related Projects: Project tree
http://rubyforge.org/softwaremap/trove_list.php?form_cat=252

Reference
http://www.jsbi.org/journal/GIW03/GIW03P191.pdf