8. There are some differences
Technical Author API Writer
Task-based content Reference-based content
To a non-technical audience To a technical audience
Re-use content Single use
Localise English only
17. Search carried out on 15/2/2016
Of the 5,000 UK
Technical Authors
on LinkedIn
173
included “API” in their
profile
18. Finding a unicorn
“Finding a technical writer who
commands
a high degree of English language
fluency
in addition to possessing a deep
technical knowledge of Java, Python,
C++, .NET, Ruby, and more
is like finding a unicorn.”
Tom Johnson
Flickr image: Owlana
19. Not an easy problem to solve
Especially someone with 5+
year’s REST API writing
experience
In the USA, rates are 1.5 to 2
times that of non-API jobs
The work can be seen as
boring
22. Technical Authors’ tools
Complex tools for complex
problems
Built to suit the needs of the
organisation
Structured authoring
Versioning
Multilingual
49. Set realistic expectations
You are more likely to find
someone with a wide and
shallow understanding of
programming
Look for writers who can read
code, rather than write it
50. Set realistic expectations
Developers should not
abdicate responsibility
Developers may need to
create the code examples
Have clear requirements
Don’t ask the author to invent
something that takes the best
from other API documentation
sites
Image: Simon Greig
51. Docs are a team
responsibility
You should be one team
Docs should be part of
the definition of Done
Docs should be part of
the review process
Image: St Helens RFC