# From Laminated Pages to Petabytes: Why I'm Joining the Ceph Foundation

DevFeed: [From Laminated Pages to Petabytes: Why I'm Joining the Ceph Foundation](<https://devfeed.tech/articles/from-laminated-pages-to-petabytes-why-i-m-joining-the-ceph-foundation-12333.md>)

Original publisher: [Read original article](<https://ceph.io/en/news/blog/2026/from-laminated-pages-to-petabytes/>)

Author: Emmanuel Ameh

Published: 2026-05-06T00:00:00Z

Content type: article

Language: en

Sources: [Ceph Blog](<https://devfeed.tech/sources/ceph-blog.md>)

Topics: [Usability](<https://devfeed.tech/topics/usability.md>), [Software](<https://devfeed.tech/topics/software.md>), [systems](<https://devfeed.tech/topics/systems.md>), [incident](<https://devfeed.tech/topics/incident.md>), [Disk image](<https://devfeed.tech/topics/disk-image.md>), [CRUD](<https://devfeed.tech/topics/crud.md>)

Tags: [blog-post](<https://devfeed.tech/tags/blog-post.md>), [ceph](<https://devfeed.tech/tags/ceph.md>), [community](<https://devfeed.tech/tags/community.md>), [developer](<https://devfeed.tech/tags/developer.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [en-article](<https://devfeed.tech/tags/en-article.md>), [en-blog-post](<https://devfeed.tech/tags/en-blog-post.md>), [guide](<https://devfeed.tech/tags/guide.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [incident](<https://devfeed.tech/tags/incident.md>), [logging](<https://devfeed.tech/tags/logging.md>), [production](<https://devfeed.tech/tags/production.md>), [software](<https://devfeed.tech/tags/software.md>), [storage](<https://devfeed.tech/tags/storage.md>), [systems](<https://devfeed.tech/tags/systems.md>), [technical](<https://devfeed.tech/tags/technical.md>), [usability](<https://devfeed.tech/tags/usability.md>), [validation](<https://devfeed.tech/tags/validation.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

## AI overview

A new Ceph Foundation technical writer explains a documentation philosophy centered on usability and practical outcomes. The article introduces test-driven documentation: validate commands and workflows in clean environments, log user friction, and organize information so urgent how-to guidance is easy to find while deeper explanations remain accessible.

## Source excerpt

Hello, Ceph Community! I'm Emmanuel Ameh, and I'm thrilled to be joining as your new Technical Writer. My path into technical writing started during a university internship at a manufacturing plant, where I was handed a problem that, looking back, shaped how I think about documentation to this day. The first piece of documentation I wrote was a one-page troubleshooting guide. It was a simple list of common production-line issues and their fixes, taped to a workstation. But it worked. Operators stopped escalating the same problems, uptime held steady, and that single laminated page did the job of a dozen phone calls. I think about that page a lot. It wasn't elegant. It wasn't comprehensive. It didn't win any awards. But it sat exactly where the people who needed it could find it, and it told them exactly what to do. That, to me, is what good documentation looks like, whether it's protecting a production line or a petabyte-scale storage cluster. That experience taught me my core philosophy: good documentation isn't measured by how thorough it looks. It's measured by what it lets people do. A doc that keeps a cluster running is worth more than a hundred pages nobody reads. That belief is what brings me to the Ceph community today. My Approach: Test-Driven Documentation ¶ My background is in enterprise software and developer advocacy, where I've focused on making complex systems feel approachable. I treat usability as seriously as technical accuracy. To me, a "perfectly correct" doc that a user can't follow is a broken feature. I advocate for test-driven documentation. In practice, this means: Validation: Running every command and workflow in a clean environment to ensure it actually works. If a tutorial says "run this, and you'll see X," then somewhere, on a fresh install, I should be able to run it and see X. If I can't, neither can the reader. Friction Logging: Identifying the exact moment a newcomer gets stuck and smoothing that path. The most valuable feedback I ca