PEPpy proposals to make Python 3 imminently maintainable
Following the Python community's PEP8 standards is a great start, but it's not the full solution for maintainable code nor even readability. In this presentation, I'll take you through the bees knees of solid coding practices from modular design to inversion of control with concrete examples of best practices. These will range from the deceptively simple to the curiously compact.
- Does style *really* matter? (Yes!)
- Where do I change the API connector -- everywhere? (No.)
- Wash, lather, rinse, repeat. (Not really, but doing things once does go a long way.)
- Just deploy my application! (It would be *easy* if it were parameterized.)
Come join us for a great programming primer for Python 3 developers of all backgrounds with an emphasis on making applications deployable, maintainable and debuggable. And, please note that the content of this presentation presents code that eases the support burden for everyone from maintainers to deployers.