| Foundations of Agile Python Development Contributor(s): Younker, Jeff (Author) |
|
 |
ISBN: 1590599810 ISBN-13: 9781590599815 Publisher: Apress OUR PRICE: $40.49 Product Type: Paperback - Other Formats Published: June 2008 Annotation: Authored by a well-known member of Python's Agile community, this is the first book to apply the most sought-after principles to Python developers, introducing both the tools and techniques built and supported by the Python community. |
| Additional Information |
| BISAC Categories: - Computers | Software Development & Engineering - General - Computers | Programming Languages - Python |
| Dewey: 005.133 |
| LCCN: 2008300950 |
| Series: Expert's Voice in Open Source |
| Physical Information: 0.86" H x 7.1" W x 9.28" (1.46 lbs) 416 pages |
| Descriptions, Reviews, Etc. |
| Publisher Description: If you're embarking on a Python development project, then you should buy this book--there's nothing quite like it. I know this because I was looking for it last year, and I couldn't find it. This book introduces the tools you'll need to get started on agile projects in Python, and unlike any other book out there, it shows you how to tie them all together. Sure, there are many good books on agile development. A lot of them cover the devel- ment processes in great detail, and this is a good thing. Agile development is very much about human interactions and the environment surrounding software development, but there is a whole ecology of tooling to make everything work at a practical level. Agile development eschews extensive up-front specification, and it anticipates that the product will constantly change, but it puts in place rigorous checks to compensate for anti- pated change. Testing is an integral part of agile development from the very start, and it is pursued with ferocious rigor. You need software tools to facilitate testing. Agile projects have very short release cycles, and this has implications for tooling, too. There's no way to have two-week release cycles if it takes you days to integrate changes, days to perform QA, and days to package and deploy the software. This means that agile devel- ment puts a high value on build and release automation. |