canmove, Confirmed users
901
edits
WebAPI/DesignGuidelines: Difference between revisions
Jump to navigation
Jump to search
→Standardizing a Feature
(Note that as one increase their experience, they should solve bigger problems (courtesy dbaron)) |
|||
| Line 43: | Line 43: | ||
** multiple proposals are good so don't be attached to your design in case it doesn't survive. | ** multiple proposals are good so don't be attached to your design in case it doesn't survive. | ||
** solving the problem you set out to solve is more important than your proposed API getting standardized. | ** solving the problem you set out to solve is more important than your proposed API getting standardized. | ||
* in advance, answer questions you anticipate and point people to the answers. | * in advance, answer questions you anticipate and point people to the answers when they ask related questions. | ||
* if you don't get responses, ask people you know who are more well-known in that community. | * if you don't get responses, ask people you know who are more well-known in that community. | ||
* "it takes a village to raise an API". | * "it takes a village to raise an API". | ||