Eighteen months ago, a scrappy team of technical communicators got together to create what they (we) wanted to see in the world — an approachable book about creating technical documentation for the developers we know and love. There are a lot of times that it isn’t possible to hire a dedicated writer, but that doesn’t mean documentation can be ignored.

We are all like a corgi confronted by a computer sometimes

A lot has happened since then, but we are so happy and so proud to tell you that by the end of summer, you’ll be able to buy Docs for Developers: An Engineer’s Field Guide to Technical Writing!

A dark-grey background with a neon-green hand drawing of a desk, showing paper notes, a monitor, keyboard and hands, glasses, mouse, smartphone. The title says Docs for Developers: An Engineer's Field Guide to Technical Writing
Cover for our book, Docs for Developers: An Engineer’s Field Guide to Technical Writing

If you’d like to be notified about our progress, please sign on to this very low-traffic, never-to-be-sold mailing list: docs-for-devs@googlegroups.com, follow us on twitter at @docsfordevs, or sign up for RSS below.

Thanks and happy writing,

Jared Bhatti

Zachary Sarah Corleissen

Jen Lambourne

David Nunez

Heidi Waterhouse

Your tech writing word-herders