Code Access Limitations

Do not modify the code once it's on the staging server for testing. As a developer, you should not have access beyond the development server. In the typical web-based development environment, development and unit testing occur on the developer's machine, manual or automated integration testing is done on the development server, acceptance testing is done on the staging server, and the production server is used for live deployment. After the code is checked into source code control, it should be moved to the development server for testing and tweaking, but developers should not make further changes beyond that point. The staging manager should package and deploy the code to the staging server for the QA team, while users should not touch anything on the development server. Only the release manager should have access to both the development and staging servers. In no circumstances should a developer have access to the production server. Any issues should be handled by support staff, who can either fix the problem themselves or request that the developer fix it on the development server. Making changes on the production server is not acceptable and can lead to major programming disasters. #SoftwareDevelopmentBestPractices

I would love to hear your input on this topic! Please feel free to share your perspective by leaving a comment below.