Dana Fried (tess@mastodon.social)'s status on Saturday, 16-Nov-2024 02:34:59 JST

@tedmielczarek okay here are my general recommendations for APIs:

1. don't leak implementation details; APIs should be conceptual and well-named; using an API should be like writing English

2. fewer methods is always better

3. if the client has to call multiple methods in a specific order with specific parameters for the subsequent calls to work, no they don't (my wife named this the "no spellcasting" rule)

4. any output object that holds resources should be scoped