Yet, for many students, biologists, and even computer scientists, the question is: “Where do I begin?” With so many platforms, books, and tutorials available, it’s easy to feel overwhelmed.

To make it easier, I’ve compiled 10 excellent resources — ranging from beginner-friendly introductions to advanced computational genomics courses. Many of these are freely available, created by pioneers in the field, and widely used in classrooms and research labs worldwide.

Whether you are a complete beginner or looking to strengthen your foundations, these courses will help you build the skills needed to analyze biological data, design workflows, and think computationally about complex biological systems.

1. HarvardX Data Analysis for Genomics by Rafael Irizarry

From the almighty Rafa, this set of online courses (via edX/HarvardX) is a classic starting point for genomic data science and bioinformatics.

2. Applied Computational Genomics – Aaron Quinlan

Aaron Quinlan (creator of bedtools and many other tools) has made his course materials open. A practical, tool-driven genomics introduction.

3. Bioinformatics Algorithms (Coursera + Companion Book)

Find the highly visual video classes on Coursera, backed by the popular Bioinformatics Algorithms book.

4. The Biostar Handbook

Not a course per se, but a hands-on manual by Istvan (founder of Biostars.org) that’s even used in classes at Penn State.

5. Introduction to Bioinformatics and Computational Biology (by Shirley Liu)

A comprehensive introduction from Shirley Liu’s lab (Harvard DFCI). Covers both theory and computational practice.

6. Data Carpentry: Genomics Workshops

Community-driven training workshops that focus on practical, reproducible research. I was honored to serve as curriculum committee chair here.

7. Computational Genomics: Applied Comparative Genomics

From the Schatz Lab — applied comparative genomics with real-world data.

8. Introduction to Computational Biology (Mike Love, creator of DESeq2)

This course bridges statistics, biology, and computation — a solid primer for anyone entering computational biology.

9. MIT Computational Biology (6.047 / 6.878 / HST.507) by Manolis Kellis

Covers genomes, networks, evolution, and health. A deep-dive from MIT’s OpenCourseWare archive.

10. An Introduction to Applied Bioinformatics

An interactive textbook with Python code, designed for practical applied bioinformatics learning.

Before you go down that path, consider this critical biological question:
Are you sequencing human cells—or bacterial contamination?

The Silent Saboteur: Mycoplasma in Cell Cultures

Mycoplasma contamination remains one of the most widespread and underdiagnosed issues in tissue culture work. Studies suggest that 15–35% of cell lines in use may be contaminated, often without visible signs. Unlike other microbial infections, Mycoplasma does not produce cloudiness, odor, or a change in pH. Many researchers won’t detect it unless they specifically test for it.

The consequences, however, are profound. Mycoplasma can significantly alter:

• Host gene expression patterns

• Cell proliferation rates

• Epigenetic profiles and chromatin accessibility

• Cytokine signaling and immune responses

In short, it can skew your results, compromise your biological conclusions, and invalidate weeks or months of research.

A Simple Diagnostic Step: Map Against Mycoplasma Genomes

If you encounter poor alignment rates to the human genome, consider mapping your reads to a Mycoplasma reference genome—or better yet, use a combined human + Mycoplasma reference. There have been cases where over half of all reads, initially assumed to be from human cells, were in fact bacterial in origin. This check is fast, easy, and could save your project.

How Contamination Happens—and Persists

Mycoplasma is small (0.1–0.3 μm), lacks a cell wall, and can pass through standard filters undetected. Common sources include:

• Contaminated reagents (e.g., FBS)

• Infected cell lines obtained from other labs

• Poor aseptic technique or shared equipment

Once present, it spreads quickly between cultures and can persist for months, silently affecting results.

Why Treatment Is Difficult

While antibiotics such as Plasmocin or BM-Cyclin are sometimes used, they often offer only partial resolution and may themselves alter cell behavior. In many cases, the best course of action is to discard the contaminated culture and start with a fresh, verified stock.

Practical Recommendations for Researchers

• Routinely test for Mycoplasma using PCR, qPCR, or fluorescence-based assays

• Incorporate contamination screens into your sequencing QC pipeline

• Use combined reference genomes when mapping ambiguous reads

• Practice strict aseptic technique and monitor all incoming cell lines

• Don’t ignore unexplained data anomalies—they might point to contamination

Closing Thought: Contamination Is a Biological Variable

It’s easy to view poor mapping as a technical issue, but sometimes the problem lies deeper—in the biology itself. Mycoplasma contamination doesn’t just interfere with sequencing; it interferes with science. As a research community, we must treat contamination not as an afterthought, but as a key variable to control.

So next time your reads won’t align, don’t just tune the aligner. Ask if your cells are telling the truth—or if they're hiding something.

Population genetics: A concise guide. John Gillespie.The Johns Hopkins University Press (1997)•

Population genetics. J. S. Gale. Wiley (1980)•

Evolutionary genetics. John Maynard-Smith. Oxford University Press (1998)•

The growth of biological thought. Ernst Mayr. Harvard University Press (1985)•

Guns, germs and steel. Jared Diamond. W. W. Norton (2007)•

Evolutionary theory: Mathematical and conceptual foundations. Sean Rice. Oxford University Press (2004)

https://fhs.mcmaster.ca/gupta-lab/index.html

Few places in Europe where good (and @some places no tution fees) master bioinformatics courses and recommended are:

KU Leuven, Belgium

http://onderwijsaanbod.kuleuven.be/opleidingen/e/CQ_50269018.htm

ETH, Zurich

http://www.cbb.ethz.ch/

University of Copenhagen, Denmark

http://studies.ku.dk/masters/bioinformatics/

University of Helsinki, Finland

http://www.cs.helsinki.fi/en/mbi/

Stockholm University, Sweden

http://www.sbc.su.se/masters/

Universities in Netherlands

http://www.nbic.nl/education/msc-programmes/

TUM , Munich Germany

http://www.mastersportal.eu/studies/865/bioinformatics.html

University of Bergen, Norway

http://www.uib.no/en/studieprogram/MAMN-INF/BI/plan

Goethe-University in Frankfurt am Main

http://www.uni-frankfurt.de/58444439/mabi

Other links:

http://www.masterstudies.com/Masters-Degree/Bioinformatics/Europe/

https://studyinsweden.se/programmes/?query=bioinformatics&period=ht-2016&level=ma&subject=natural-science&university=#search

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

Address of the bookmark: http://gtpb.igc.gulbenkian.pt/bicourses/index.html

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.

Date : June 10-13

Organizers: The Society for Bioinformatics in Northern European countries (SocBiN) and the Norwegian Bioinformatics Platform / ELIXIR.NO

Venue: Department of Informatics, University of Oslo, Norway

Topics:
Tools and technologies for integrative bioinformatics
Metagenomics
Comparative genomics and phylogeny
Post-ENCODE bioinformatics
Gene regulation
Cancer genomes
Marine 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