|
|
|
|
|
by Communitivity
928 days ago
|
|
I would like to see not just code, but also a discussion of the tradeoff decisions made when creating that code, and a discussion of what could be done or looked at next. Even with an example written for an article, if it's non-trivial then there will have been trade-off design decisions. In some ways, understanding the reasoning behind tradeoff decisions to make when using an SDK is more important than an example that shows me what arguments to use when calling a specific function. For example, you have an article about Python and your checking the size of the array. Don't just tell me it's len(my_array), explain the decision to do that. As an aside in case your interested, as I understand it the reasoning is to implement length via a strategy pattern: any object which has a concept of length can implement a __len__ method, and len() will then use that method to get the length, which allows a lot more flexibility without having multiple ways to do length. |
|