10 myths about API documentation - Dashboard
VIEWED
662
STARTED
25
COMPLETED
25
COMPLETION RATE
100%
DROP OUTS
0
TIME TO COMPLETE
11 mins
 
Countries Responses
US 40.00%
IN 16.00%
AU 12.00%
CA 12.00%
PL 4.00%
BY 4.00%
GB 4.00%
HK 4.00%
NZ 4.00%
Total 100.00%
You must read source code to write API docs.
Answer Count Percent
20% 40% 60% 80% 100%
Generally true 11 44%
Generally false 14 56%
Other 0 0%
Total 25 100 %
You must read source code to write API docs. - Text Data for Other
No Data To Display
You'll need to extrapolate sample code from one language to create code samples in another.
Answer Count Percent
20% 40% 60% 80% 100%
Generally true 4 16%
Generally false 19 76%
Other 2 8%
Total 25 100 %
Youll need to extrapolate sample code from one language to create code samples in another. - Text Data for Other
10/03/2019 45699406 it's not a bad approach.
You must be a former engineer to be competitive in the API doc space.
Answer Count Percent
20% 40% 60% 80% 100%
Generally true 6 24%
Generally false 19 76%
Other 0 0%
Total 25 100 %
You must be a former engineer to be competitive in the API doc space. - Text Data for Other
No Data To Display
Technical writers usually create the API reference content (e.g., OpenAPI spec, Javadoc).
Answer Count Percent
20% 40% 60% 80% 100%
Generally true 7 28%
Generally false 18 72%
Other 0 0%
Total 25 100 %
Technical writers usually create the API reference content (e.g., OpenAPI spec, Javadoc). - Text Data for Other
No Data To Display
Almost all job interviewers care about, when it comes to API doc jobs, is technical know-how.
Answer Count Percent
20% 40% 60% 80% 100%
Generally true 12 48%
Generally false 12 48%
Other 1 4%
Total 25 100 %
Almost all job interviewers care about, when it comes to API doc jobs, is technical know-how. - Text Data for Other
No Data To Display