Just Because You Can, Doesn't Mean You Should
Formal Metadata
| Title | Just Because You Can, Doesn't Mean You Should |
|
| Title of Series | |
| Part Number | 145 |
| Number of Parts | 173 |
| Author | |
| License | You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this license. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
| Production Place | Bilbao, Euskadi, Spain |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | Julian Berman - Just Because You Can, Doesn't Mean You Should
Python is a powerful language that provides many tools for creating
highly dynamic programs. It offers tools all across the complexity
spectrum that library authors can use to make their libraries seem
convenient to use for users.
While it's true that there are a wealth of techniques with huge
positive benefits, there are a number of common antipatterns which can
deceptively cause a net-loss in flexibility, readability, and
predictability for users.
We'll explore a few specific commonalities in this area of library and
object API design, and talk about the ramifications they have on each
of these programmer concerns. |
|
| Keywords | |