The Swift API guidelines are really good. They’re worth reading even if you’re not interested in Swift just to see an example of how to communicate this kind of information well. https://www.swift.org/documentation/api-design-guidelines/
@siracusa I’m not an advocate, but this is also the same basic insight that drives test driven development: the idea of thinking very clearly about what you’re trying to accomplish separately from writing implementation code.
Add comment