7 ms·
That's fair, and in hindsight, I suppose it is a little silly to try to help customers use your platform as it was meant to be used rather than having them sort
by whitfieldsdad 3y ago
That's fair, and in hindsight, I suppose it is a little silly to try to help customers use your platform as it was meant to be used rather than having them sort of guess how to use it...it'll generate revenue either way...
- mcdonje 3y agoNot sure my point came across. I did say they should document better. Customers shouldn't have to reverse engineer. But you can't account for how all of your customers are going to use your API. It is the interface. Like, you mentioned in another comment about a python package as an example of what they could offer. Should they offer Rust, Go, JS, etc., clients as well? If you buy cement, you don't expect the seller to box in the area where it should be poured. They don't have the blueprints to do that correctly. They're not building your building. The trough on the cement truck is their interface. What you do with it is your job to figure out.
- whitfieldsdad 3y agoI was moreso just saying that at least one reference implementation would be nice so I can see how they intended the product to be used, why they designed the API like they did, etc.