β
After prototyping, start again with TDD instead of trying to go back, and write tests for the prototype. Even
β
β
Kevin Harvey (Test-Driven Development with Django)
β
Testing and documentation have a crucial relationshipβyour tests prove that your documentation is telling the truth.
β
β
Kevin Harvey (Test-Driven Development with Django)
β
code without tests is a prototype at best.
β
β
Kevin Harvey (Test-Driven Development with Django)
β
There are four key practices to writing great code: Version control Documentation Testing Continuous Integration Each
β
β
Kevin Harvey (Test-Driven Development with Django)
β
Apps are often named for the main model that they contain.
β
β
Kevin Harvey (Test-Driven Development with Django)
β
>>> fill = {"name": "Blitz", "age": "30"}
>>> g = PersonDetailsForm(fill)
>>> g.is_valid()
True
>>> g.cleaned_data
{'age': 30, 'name': 'Blitz'}
β
β
Arun Ravindran (Django Design Patterns and Best Practices: Industry-standard web development techniques and solutions using Python, 2nd Edition)
β
OpenStack includes a dashboard project named Horizon, which is a web interface built with the Django framework and the different OpenStack APIs from the OpenStack services.
β
β
John Belamaric (OpenStack Cloud Application Development)
β
Jacob Kaplan-Moss, one of Djangoβs original developers, says βCode without tests is broken by design.
β
β
Nigel George (Mastering Django: Core: The Complete Guide to Django 1.8 LTS)
β
Code is read more than it is written.
β
β
Daniel Roy Greenfeld
β
An individual block of code takes moments to write, minutes or hours to debug, and can last forever without being touched again. Itβs when you or someone else visits code written yesterday or ten years ago that having code written in a clear, consistent style becomes extremely useful. Understandable code frees mental bandwidth from having to puzzle out inconsistencies, making it easier to maintain and enhance projects of all sizes.
β
β
Daniel Roy Greenfeld