About Inkwright, Inc.

I founded Inkwright, Inc. because I kept seeing the same problem from two different angles: as a software engineer watching users struggle with documentation that failed them, and as a technical writer watching engineers' brilliant work go under-appreciated because nobody explained it well. The gap between those two worlds is exactly where Inkwright lives.

My background is unusual for a technical writer. I studied software engineering at the University of Washington before earning a degree in English and Creative Writing from Southern New Hampshire University, graduating summa cum laude with a 4.0 GPA. That combination isn't an accident. I genuinely love both the precision of engineering and the craft of writing, and I've spent decades finding the place where the two meet.

I'm extraordinarily picky about documentation. That's not a polite way of saying I'm difficult to work with; it's an honest description of my standards. I believe that documentation should spend its words where users actually struggle, not where they don't. I believe that vague explanations of complex concepts are disrespectful to the reader. And I believe that great documentation is invisible in the best possible way: users simply succeed without ever having to think about why.

In February 1989, I moved to Japan, and it changed the way I see almost everything.

Japan has shaped my approach to craft more than any course or credential. The Japanese pursuit of making things the best they can possibly be, the cultural attentiveness to aesthetics, and the deep respect for doing something correctly, rather than just doing it quickly. These aren't abstract ideals to me. They're a standard I absorbed over years of living among people who embody them.

The Japanese language itself has been a lifelong passion. It is precise, layered, and deeply contextual. Japanese is a language that rewards the kind of careful attention that great technical writing also demands. I teach Japanese to members of my own family. I've returned to Japan more times than I can count, and I plan to spend my retirement there.

That connection is also why Japanese localization is a genuine capability at Inkwright, not a service we bolted on. We don't translate. We write natively in both English and Japanese, with people who understand the technology and the language equally well.

I believe that great technical writing, as well as great software, becomes more possible when more people have access to the craft. I've mentored female engineers through PyLadies and Rails Girls, and I've worked with aspiring writers in both fiction and technical writing. Watching someone find their voice, in code or in prose, is one of the things I find most satisfying about this work.

There are plenty of writing services. There aren't many that bring decades of hands-on software engineering experience, native English and Japanese proficiency, an obsessive commitment to clarity, and a philosophy of craft shaped by one of the world's most quality-conscious cultures.

That's what Inkwright is built on. If that sounds like what your documentation needs, I'd love to hear about your project.