There's a spectrum of ways to read a technical resource. On one end, you absorb every word in order. On the other, you skim for what you need and move on. This site is designed to support both approaches, but it works best when you know what you're looking for.
The Layered Approach
Each chapter is structured in layers of depth.
The opening section always gives you the high-level picture — the kind of thing you'd want to remember if you only had five minutes. If you're skimming before a meeting or refreshing something you once knew, this is enough.
The middle sections go deeper. They're where the analogies live, where the mechanisms get explained, where the "but wait, how does that actually work" questions get answered. This is the main reading path.
The end of each chapter either connects the concept to adjacent ideas or points toward a practical application. Some chapters end with a diagram; some end with a list of the things that can go wrong.
Don't try to memorize this material. The goal is building mental models, not vocabulary tests. If you read something, understand it well enough to explain it in a sentence, and then forget the exact term — that's fine. The term will come back faster the second time, and the model stays.
Computational Analogies
The analogies in this site are marked with a green sidebar and labeled Computational Analogy. They look like this:
This is what a computational analogy looks like. It pairs a biological concept with a software equivalent and explains the structural similarity — not just the surface resemblance.
These are not loose metaphors. They're chosen because the mechanisms genuinely parallel each other. But analogies have limits — the similarity breaks down somewhere, and when it does, the text will say so.
Read the analogies actively. After reading one, pause and ask: where does this mapping break? What would the equivalent look like in code? Where does the biological system do something the software one can't?
Code Examples
The In Practice chapters at the end of each part contain runnable code. They use real tools from the bioinformatics ecosystem: Biopython, NetworkX, MNE-Python, pandas, and others.
In Practice sections look like this. They're marked with a cyan sidebar. The code examples in these sections are real — they run against real biological data and produce real output. The data sources are free and publicly accessible.
You can run the code examples on your own machine. Each In Practice chapter tells you what to install and where to get the data. The code is annotated, but the annotations focus on the biology — what the function is doing in biological terms, not just what the Python call does.
Inline code references look like this and refer to specific functions, parameters, or values mentioned in the surrounding text.
What to Skim, What to Absorb
Not everything needs the same attention.
Skim when: you're reading Part 0, which is orientation material. You're reading a chapter you've touched before and just need a refresher. You're reading late at night.
Absorb when: you hit the Central Dogma (2.6), because everything in the curriculum references it. You hit any chapter in Part 3 on gene regulation, because it fundamentally changes how you think about what DNA "does". You hit any In Practice chapter in your specific domain.
Parts 0 and 1 are foundational but move fast. Parts 2 and 3 are where the real machinery lives. Parts 4 through 8 are more modular — you can follow the paths that matter most to your work.
A Note on Depth
This site goes deeper than most introductions, but shallower than a graduate course. It's calibrated for the level of understanding you need to work productively in a bioinformatics or computational biology role — not to pass a cell biology exam.
When a topic comes up that we're necessarily simplifying, the text will say so. Biology is full of exceptions, edge cases, and "actually it's more complicated than that." We won't pretend otherwise. We'll just make sure the simplification is useful before we acknowledge its limits.
If you finish this site and find yourself wanting to go deeper — good. The glossary, the references, and the links in each chapter will take you there.