The Hitchhiker's Guide to Python Quotes

Rate this book
Clear rating
The Hitchhiker's Guide to Python: Best Practices for Development The Hitchhiker's Guide to Python: Best Practices for Development by Kenneth Reitz
211 ratings, 3.93 average rating, 22 reviews
Open Preview
The Hitchhiker's Guide to Python Quotes Showing 1-6 of 6
“Some people believe best practice is to install nothing except virtualenv and Setuptools and to then always use virtual environments.”
Kenneth Reitz, The Hitchhiker's Guide to Python: Best Practices for Development
“tl;dr means “Too long; didn’t read,” and apparently existed as editor shorthand before popularization on the Internet.”
Kenneth Reitz, The Hitchhiker's Guide to Python: Best Practices for Development
“Write a breaking test if you want to take a break If you are in the middle of a development session and have to interrupt your work, it is a good idea to write a broken unit test about what you want to develop next. When coming back to work, you will have a pointer to where you were and get back on track faster.”
Kenneth Reitz, The Hitchhiker's Guide to Python: Best Practices for Development
“Pure functions are deterministic: given a fixed input, the output will always be the same.”
Kenneth Reitz, The Hitchhiker's Guide to Python: Best Practices for Development
“Spaghetti code Multiple pages of nested if clauses and for loops with a lot of copy-pasted procedural code and no proper segmentation are known as spaghetti code .”
Kenneth Reitz, The Hitchhiker's Guide to Python: Best Practices for Development
“If you want to work for a large company in any sort of IT role, a functioning awareness of Vi is necessary. 3 Vim is much more featureful than Vi, but is close enough that a Vim user can function in Vi.”
Kenneth Reitz, The Hitchhiker's Guide to Python: Best Practices for Development