# Rob Patro

- Researcher: Rob Patro
- Role: Professor leading COMBINE-lab (post says "as a professor" and mentions teaching undergraduates at UMD; no title line on page)
- Field: genomics
- Tools: Claude (Sonnet, Opus); Claude Code (Opus 4.6); GitHub Copilot (web, CLI, VS Code)
- Published: 2026-02-15
- Source: https://combine-lab.github.io/blog/2026/02/15/a-skeptics-guide-to-generative-ai-coding.html
- Older account (before March 2026). Latest flagship models when written: Claude Opus 4.6 and GPT-5.2. Latest now: Claude Opus 5.5 and GPT-6.1 Sol. Agent tools have also changed since, so check whether a limitation reported here still applies.

## What they did

Patro, a self-described skeptic, describes a series of ports and features done with AI coding agents in his lab's genomics software: the mim index core, a Cuttlefish in-memory tile collation feature (about five times faster), sshash and piscem translated to Rust. Claude Code (Opus 4.6) translated the piscem mapping tool in about a day and a half, wrote the binary-file equivalence test harness and unit tests, instrumented a slow index build and fixed a cache-incoherent access pattern. He reports 100 percent concordance between the C++ and Rust versions on non-trivial test data across assay types.

## In their words

> "It was not a “one shot” solution; there were some hiccups in how multi-part archives were handled."

> "In one step, Claude replaced what was an efficiently encoded Elias Fano sequence with O(1) select support with a Vec<u64> with a binary search."

## Lessons they draw

- Watch the process: he caught a silly data-structure substitution only because he was reading along (Patro).
- Where the agent introduced a concurrency bug he located the cause himself; its fix was sub-optimal until he explained his better one (Patro).
- Despite explicit instructions to follow the C++ data structures, Claude invented a different encoding; he kept it on a branch and had it produce the equivalent (Patro).
- Have the agent write the equivalence test harness and tests, and ask for a phased implementation plan with correctness criteria per phase (Patro).

## Limits of this account

Software-porting tasks in the author's own codebases; I read the post in two parts and did not read the final sections.
