Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Expert Python Programming

You're reading from   Expert Python Programming Become a master in Python by learning coding best practices and advanced programming concepts in Python 3.7

Arrow left icon
Product type Paperback
Published in Apr 2019
Publisher Packt
ISBN-13 9781789808896
Length 646 pages
Edition 3rd Edition
Languages
Arrow right icon
Authors (2):
Arrow left icon
Michał Jaworski Michał Jaworski
Author Profile Icon Michał Jaworski
Michał Jaworski
Tarek Ziadé Tarek Ziadé
Author Profile Icon Tarek Ziadé
Tarek Ziadé
Arrow right icon
View More author details
Toc

Table of Contents (25) Chapters Close

Preface 1. Section 1: Before You Start
2. Current Status of Python FREE CHAPTER 3. Modern Python Development Environments 4. Section 2: Python Craftsmanship
5. Modern Syntax Elements - Below the Class Level 6. Modern Syntax Elements - Above the Class Level 7. Elements of Metaprogramming 8. Choosing Good Names 9. Writing a Package 10. Deploying the Code 11. Python Extensions in Other Languages 12. Section 3: Quality over Quantity
13. Managing Code 14. Documenting Your Project 15. Test-Driven Development 16. Section 4: Need for Speed
17. Optimization - Principles and Profiling Techniques 18. Optimization - Some Powerful Techniques 19. Concurrency 20. Section 5: Technical Architecture
21. Event-Driven and Signal Programming 22. Useful Design Patterns 23. reStructuredText Primer 24. Other Books You May Enjoy

Summary

In this chapter, we have discussed an approach that should make documentation management an organized, lightweight, efficient, and (hopefully) fun process. We started from the seven rules of technical writing that apply to any kind of technical writing—not only documentation. From there, we have introduced tools and techniques that convert these simple rules into a clear and organized engineering process.

One of the hardest things to do when documenting a project is to keep it accurate and up-to-date. The only way to make this happen is by treating it is as a first-class engineering artefact. Good documentation is always close to the code it documents. Making the documentation part of the code repository makes this a lot easier. From there, every time a developer makes any change in the code, he or she should change the corresponding documentation as well.

A complementary...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime