Planned updates to Module 6

[andrewphilipsmith]

Discussion with @nbarlowATI and @andrewphilipsmith:

• [ ] Rename 6.2 to "Managing Dependencies and Environments" (ie include the environments in the heading to emphasise their importance)
• [ ] add something 6.4 dividing up code into sensible manageable chunks in .py files. Also, you can use packaging to hide the implementation details from consumers of your code.
• [ ] 6.6 needs a "further reading" section. Emphasise that this is a huge topic that must be adapted to individual, institutional and project settings.
• [ ] 6.8 Issues - reproduce/actual behaviour/expected behaviour (see https://www.joelonsoftware.com/2000/11/08/painless-bug-tracking). Everything else is optional - probably good practice and can be adapted to your project/team/institution.
• [ ] 6.4 packaging - mention CI/CD as a way to do packaging.

Potential for the future:

• [ ] Separate or highlight the sections which are objective statements about python, vs opinions/subjective/best practise guides about software development.

[andrewphilipsmith]

Also, to review (after having worked through the exercise ourselves):

Could the exercise be moved to earlier? eg

• talk 6.0-6.5,
• then do the exercise
• come back and have a quick debrief on the exercise
• talk 6.6-6.8