3 ms·
You need documentation not just to get your happy case working (how do I call this?), but to know things like: 1. Know whether a good behavior you're getting i
by kazinator 6y ago
You need documentation not just to get your happy case working (how do I call this?), but to know things like:
1. Know whether a good behavior you're getting is a fluke, or required.
2. If something stops working with a new release of the API middleware, is it due to their bug, or because you misused it?
3. What limitations of the API will leak through to your program? What input ranges to watch out for?
4. What unexpected situations could occur that must be handled? These won't happen if you get the happy case working, or not all of them.