> 4. Ask what is considered good code. Read it. Study it.
Any suggestions?
Any suggestions?
Another strategy is to skim the source code for your dependencies, without worrying about whether the code is good or not. You'll still get a good idea of the scope of the problem the library is solving, and whether it looks like the authors knew what they were doing. You'll have a crude map of the code in your code, useful when you run into bugs later.
The number of classes and interfaces in Twisted is a bit of a stumbling block, but I've never come across anyone with a better, more "Pythonic" way to express the same ideas or provide the same flexibility. The ABCs introduced in modern Python are inferior to the interfaces Twisted uses, and the most recent PEP I've seen for Futures is but a pale shadow of Twisted's Deferreds.
1. Reading a library you are using, even if it's a standard library like smtplib is fun and makes you smarter and your code better.
2. Python is such a joy to read, unlike some other languages.
3. Some libraries (I'll mention smtplib again) are such a mess, and yet reasons 1 + 2 still make it easy for you to learn from them, while also learning what not to do.