Best Practices in Software Development
References
Code Integrity
- Automated builds
- Continuous integration
- Unit testing and test-driven development
- Code consistency and agreed standards for quality
Best Practice to Continuous Delivery
- Don’t build the binaries at each stage of the deployment pipeline, create them once an reuse them.
- The capacity testing environment should be as similar as possible to the production environment.
- increase frequency of deployment
- iterative monitor, measure, and improve the code
- Script everything!
- Don’t let builds that fail unit or acceptance test into production
- Put all the configuration in version control (network, firewall, OS, etc)
- Automate everything
- automate code testing
- automate work-flows
- automate infrastructure
Git dos and don’ts
The dos:
Write useful, readable commit messageuse topic branches locally
small, logical commits
do choose a workflow
The don’ts:
Don’t rebase public commitsDon’t delete unmerged remote branches
Don’t more than 1 project per repo.
Don’t create a very large repo.
Labels: Architecture, Code Quality, Config Management, Continuous Integration, Design, OO, Programming, Tools, Version Control
posted by Andy Wu @ 10:36 AM
0 Comments
