You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
An API has two sides: first, the mental models underlying it, which should straightforwardly map to the mental models of domain experts. Then, the actual objects/signatures of the API. API design is mostly about designing the 1st. The 2nd is just a mechanical consequence of it.
So to design a new API, start from expert mental models and end-to-end workflows. The worst APIs I've seen originated from confused mental models. You can't create a simple language to specify how to do XYZ if you don't have a crystal clear understanding of XYZ.
Remember that the actual objects & signatures are pretty much an afterthought. Don't start with them. End with them.
Do you have any influence over the current tensorflow mess?
+1. This is the same concept that really sold test driven development to me; write code first as a user (the test) before writing code as the provider (the implementation)
I also want to say that poorly documented APIs are hell on earth. Was working on a Rust interface to a brokerage this weekend, and they just didn’t mention if their Websocket API uses SSL or not. Turns out it doesn’t (only mkt data gets sent, so no SSL is not as big a concern).
Though TBH not having SSL on anything finance related is kinda worrying
Domain driven design that is.
Mock the actual logic, build your shell around it first.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
