Stay organized with collections
Save and categorize content based on your preferences.
When you're writing reference documentation for a method, phrase the main
method description in terms of what the method does (gets, lists, creates,
searches), rather than what the developer would use it to do (get, list,
create, search).
It's a subtle distinction that manifests mostly in whether the initial verb
in the description has an -s at the end or not.
Recommended: tasks.insert: Creates a new
task on the specified task list.
Not recommended: tasks.insert: Create a
new task on the specified task list.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-10-15 UTC."],[[["When writing documentation for methods, focus on what the method accomplishes (e.g., \"creates\") rather than the developer's action (e.g., \"create\")."],["This subtle difference is mainly reflected in whether the initial verb in the description is singular or plural, with the singular form being preferred."],["Refer to Google Cloud API design guide for further details and illustrations."]]],[]]
