api-design

Ultimate goal is to use the tweepy api search to focus on topics (i.e docker) and to EXCLUDE retweets. I have looked at other threads that mention excluding retweets but they were completely applicable. I have tried to incorporate what I've learned into the code below but I believe the "if not" piece of code is in the wrong place. Any help is greatly appreciated. #!/usr/bin/python import tweepy import csv #Import csv import os # Consumer keys and access tokens, used for OAuth consumer_key = 'MINE' consumer_secret = 'MINE' access_token = 'MINE' access_token_secret = 'MINE' # OAuth process,

"API design is like sex: make one mistake and support it for the rest of your life" ( Josh Bloch on twitter ) There are many design mistakes in the Java library. Stack extends Vector ( discussion ), and we can't fix that without causing breakage. We can try to deprecate Integer.getInteger ( discussion ), but it's probably going to stay around forever. Nonetheless, certain kinds of retrofitting can be done without causing breakage. Effective Java 2nd Edition, Item 18: Prefer interfaces to abstract classes : Existing classes can be easily retrofitted to implement a new interface". Examples:

I've found myself that I tend not to have private class functions. If possible, all candidates to private class function rather I put in to unnamed namespace and pass all necessary information as function parameters. I don't have a sound explanation why I'm doing that but at least it looks more naturally to me. As a consequence I need to expose less internal details in the header file. What is your opinion - is it correct practice? In the semi large projects where I usually work (more than 2 million lines of code) I would ban private class functions if I could. The reason being that a private

Is an API endpoint the 'method', like https://api.foursquare.com/v2/venues/ or the full URL including non-query-string parameters like https://api.foursquare.com/v2/venues/5104 In other words, are these two separate endpoints or considered the same endpoint? http://myapi.com/somemodel/1 http://myapi.com/somemodel/2 According to this Wikipedia article , the endpoint is a web service, defined by a WSDL file, and does nothing more than define the address or connection point to a web service. It is typically represented by a simple HTTP URL string. Microsoft uses the term endpoint in various

I'm learning Objective-C, and have a C/C++ background. In object-oriented C++, you always need to declare your method before you define (implement) it, even if it is declared in the parent class. In procedural-style C, IIRC, you can get away with just defining a function so long as it is only called from something else in the same compilational unit (ie. the same file) that came later on in the file (well, provided you don't declare it elsewhere with "extern"). Now, in Objective-C, it appears that you only need to declare selectors in the header file if they are going to be used by something

I have often heard that jQuery has made some poor API decisions. Although jQuery is not my favourite library it's the library I've used most often and I find it hard to point out specific mistakes in the API design or how it could have been improved. What parts of jQuery's API could have been done better, how could it have been implemented different and why would that different implementation be better? The question extends to both low level individual details of the API and high level details of the API. We are only talking about flaws in the API rather then flaws in the high level design /

We have an API which randomly takes high content download time in chrome, It works fine always in firefox and takes an only few ms . The response size is 20kb uncompressed and 4kb compressed. The same request also works fine using curl. Things that we have tried: Disabling If-None-Match header to disable cache response from the browser. Trying various compressions (gzip, deflate, br). Disabling compression. Disabling all chrome extensions. The same request works fine sometimes on chrome but randomly returns very high content download time. We are unable to understand the root cause of this

For example, instead of void shared_ptr::reset() noexcept; template <typename Y> void shared_ptr::reset(Y* ptr); one may think of template <typename Y = T> void shared_ptr::reset(Y* ptr = nullptr); I think performance difference is negligible here, and the second version is more concise. Is there any specific reason the C++ standard goes the first way? The same question has been asked for the Kotlin language, and default argument is preferred there. Update: std::unique_ptr::reset() follows the default argument design (see here ). So I think the reason std::shared_ptr::reset() uses overloads is