- Documentation
- Automating Deployment Notifications on Slack
- Background Processing at DLSS
- Communication
- Deployment
- Deprecation
- How To - Readme
- Licensing
- Monitoring
- Puppet Prs
- Releasing Gems
- Setting Up Ruby Projects
- Shared Configs
- Testing
- UI/Bootstrap
- Updating NodeJS
- Updating Ruby
- Version Control
- Accessibility (Infrastructure)
- Resetting the db for a deployed Rails application
Best practices guides should attempt to answer the question:
To what extent does it make our products better?
- Easier to develop
- Easier to test
- Easier to deploy
- Easier to maintain
- Easier to understand by a new developer that has to get up to speed with the code
Or conversely, what is the level of danger if we don't agree and everyone does it differently?
Best practices should represent existing or emerging consensus within the department. Where possible, best practices should refer to open source documentation for further information and, especially, any useful getting started guides.
Best practices should also be generally applicable, and describe a high level of practice (so that, they too, are easier to develop, deploy, maintain and learn).