Explore code to write technical documentation
A technical writer uses Devin to explore code before documenting it, plus a Slack writing agent built on Devin, reporting about 20,000 lines of docs per month.
What they did
Fern's only technical writer, Devin Logan, uses the Devin AI engineer, which already has context on all of Fern's repos, to explore code before writing. She also tags Fern Writer, a Slack agent built on Devin, with an engineering thread, and it opens a PR with drafted pages, reorganized content and redirects. She then pulls the branch and iterates locally with Claude Code.
How it went
She reports about 20,000 new lines of docs per month across roughly 500 pages. She reviews and edits every page, often heavily. Fern Writer's first drafts sometimes got the structure wrong or skipped a changelog entry.
Worth knowing
Engineer review still mattered: in one rewrite of the authentication docs, the engineer found the conceptual framing wrong, which forced a restructure.
Labels
Fern's only technical writer, Devin Logan, uses the Devin AI engineer, which already has context on all of Fern's repos, to explore code before writing.
Fern's only technical writer, Devin Logan, uses the Devin AI engineer, which already has context on all of Fern's repos, to explore code before writing.
She also tags Fern Writer, a Slack agent built on Devin, with an engineering thread, and it opens a PR with drafted pages, reorganized content and redirects.
She also tags Fern Writer, a Slack agent built on Devin, with an engineering thread, and it opens a PR with drafted pages, reorganized content and redirects.
She reports about 20,000 new lines of docs per month across roughly 500 pages. She reviews and edits every page, often heavily.
The “Material” label failed its quality check and is not used for selection.
Details
- Agents
- Devin
- Source
- other
- Source date
- Mar 10, 2026
- Accounts
- 1
- In registry since
- Oct 12, 2026