3 ms·
This is good advice especially for developer tools. Start with the API interface first: 1. Ask what problems the tool intends to solve 2. Then ask what's the
by rmbyrro 4y ago
This is good advice especially for developer tools.
Start with the API interface first:
1. Ask what problems the tool intends to solve
2. Then ask what's the best experience for developers to command or program it
"Best experience" depends on the context. A few factors worth consideration are:
- Succinctness
- Easiness to understand
- Memorability
- Clarity
- Familiarity (if developers are already used to some existent API)
Then build whatever is needed to make that API get developers from point A to point B.