The DNA Jigsaw

A genome is a single text billions of letters long — but no machine can read it straight through. Sequencers instead chop many copies into millions of short reads and hand you the shuffled pile. Your job: glue them back into the original, using the fact that reads from nearby places overlap.

It's exactly like reassembling a shredded document, or a jigsaw with no picture on the box. Where two fragments share an overlapping edge, you can join them. Do it enough and the original emerges.

That's genome assembly, and the trap is hiding in plain sight: genomes are full of repeats — the same stretch appearing many times. A repeated region looks like it could connect to several places, and suddenly the puzzle has multiple plausible solutions. That ambiguity is what makes assembly, formally, NP-hard.

Try it. Below are shuffled fragments of a hidden DNA sequence. Click them in order to lay them on the assembly track — the demo automatically merges overlapping ends. Rebuild the original as short as possible.

<p class="hint">{{hint}}</p>
<div class="reads" id="reads"></div>
<div class="track-wrap"><span class="lab">{{lab_assembly}}</span><div class="track" id="track"></div></div>
<div id="result" class="result"></div>
<div class="btns">
  <button id="auto" type="button">{{btn_auto}}</button>
  <button id="reset" type="button" class="ghost">{{btn_reset}}</button>
</div>

* { box-sizing: border-box; }
body { font-family: system-ui, sans-serif; color: #222; margin: 0; }
.hint { font-size: .9rem; color: #444; margin: 0 0 .8rem; line-height: 1.45; }
.hint b { color: #c0392b; }
.reads { display: flex; flex-wrap: wrap; gap: .4rem; margin-bottom: 1rem; }
.read { font: 800 15px ui-monospace, monospace; letter-spacing: 1px; background: #fff; border: 2px solid #457b9d; color: #1d3557; border-radius: 8px; padding: .4rem .6rem; cursor: pointer; }
.read:hover { background: #f0f4f8; }
.read.used { opacity: .35; cursor: default; }
.track-wrap { display: flex; align-items: center; gap: .5rem; margin-bottom: .8rem; flex-wrap: wrap; }
.lab { font: 600 13px system-ui; color: #555; }
.track { display: flex; flex-wrap: wrap; gap: .3rem; min-height: 2.2rem; flex: 1; }
.chip { font: 800 14px ui-monospace, monospace; background: #2a9d8f; color: #fff; border-radius: 6px; padding: .35rem .5rem; cursor: pointer; }
.result { font: 800 16px ui-monospace, monospace; letter-spacing: 1px; word-break: break-all; min-height: 1.5em; margin-bottom: .4rem; }
.verdict { font: 700 14px system-ui; min-height: 1.3em; margin-bottom: .6rem; }
.verdict.ok { color: #0a7d33; } .verdict.bad { color: #b9770e; }
.btns { display: flex; gap: .5rem; }
button { font: 600 14px system-ui, sans-serif; padding: .5rem 1rem; border: 1px solid #457b9d; background: #457b9d; color: #fff; border-radius: 8px; cursor: pointer; }
button.ghost { background: #fff; color: #457b9d; }

// Code not found

When you've placed them all, the assembly shows whether you matched the original. Press Auto-assemble to let a greedy overlap method try — and notice how the repeated stretch can lure it into the wrong join. That single ambiguity is the whole difficulty of assembly in miniature.

Assembly is a beautiful tangle of classic hard problems:

• Checking is easy. Given a proposed sequence, confirm every read appears in it.
• The natural model is NP-hard. Finding the shortest string containing all reads (the shortest common superstring) is NP-hard, and ordering reads by overlap is a Hamiltonian-path-style problem — visit every read once along overlaps.
• Repeats are the villain. If a sequence longer than your reads occurs twice, the data literally can't tell which copy a read came from. No algorithm can resolve what the information doesn't contain.
• De Bruijn graphs to the rescue. Modern assemblers break reads into k-mers and build a graph where assembly becomes finding an Eulerian path (visit every edge once) — far more tractable than the Hamiltonian version, and the workhorse of real tools.
• Long reads change the game. Newer sequencers produce much longer reads that span repeats, dissolving the ambiguity at the source — the biggest practical leap in assembly.

So genome assembly is where shortest-superstring, Hamiltonian and Eulerian ideas all meet biology — hard in theory, tamed by clever graphs and better data.

Assembly is the first step that makes genomics possible:

• Personalized medicine: reading a patient's genome to tailor treatment.
• Disease research: finding the genetic basis of conditions and cancers.
• Evolutionary biology: comparing species' genomes to trace the tree of life.
• Pathogen surveillance: assembling new virus and bacteria genomes — as done worldwide for COVID variants.
• Agriculture and conservation: improving crops and understanding endangered species.

Every reference genome you've heard of — human, wheat, the latest virus — exists because assembly algorithms stitched millions of fragments into a whole.

Genome assembly is a jigsaw with a cruel twist: many of the pieces look alike. Those repeats are the source of its NP-hardness — not a lack of cleverness, but a genuine ambiguity baked into the data. Stitch the fragments and the original usually emerges; near a repeat, the puzzle can branch into several equally valid stories.

What's inspiring is how the field answered: not by solving the NP-hard problem head-on, but by reframing it (de Bruijn graphs make it an Eulerian walk) and by changing the data (long reads that span repeats). Reading the code of life went from a moonshot to a routine — a vivid reminder that the way around a hard problem is often a better question, or better measurements, rather than brute force.