That is fine with regards to dev systems, but absolutely not on prod systems. If you think that developers should have full control to prod systems then you are clearly not a professional developer who understands dev/test/prod concepts.
In typical and predictable fashion, the Developers think that they NEED full control of everything in order to do their jobs. This has almost never proven to be the actual case, it is just the standard "pat" answer that all developers give because they do not want ANY limitations put on them. There is almost never any regard given to Best Practice and Enterprise Standards for security and configuration creep by developers. They tend to download whatever they feel like downloading onto production servers. Surprisingly, I have know very few developers that "prefer" to operate in a defined, locked-down, and structured change management system.
Most developers I have dealt with do not draw much distinction between a dev environment and a prod environment. They tend to do whatever is convenient for them and create absolute chaos and security issues. This, of course, does not apply universally, but it has been the case with most developers I have worked with in my 20 years of engineering experience.
Most developers love to operate with autonomy and as if they are in a small mom and pop environment. Only the true development professionals that I have worked with understand how structure helps them and the enterprise, rather than viewing "rules" as an enemy in the way of their ability to get the job done.
Giving local admin rights on production servers is the lazy way to accomplish what needs to get done. Developers need to understand that it is the Engineers and Admins duty to protect the enterprise and maintain viable recovery point objectives.
In a true enterprise, It should not be the wild west, where the developers are the gunslingers doing whatever they please.
Slashdot Mirror
That is fine with regards to dev systems, but absolutely not on prod systems. If you think that developers should have full control to prod systems then you are clearly not a professional developer who understands dev/test/prod concepts.
In typical and predictable fashion, the Developers think that they NEED full control of everything in order to do their jobs. This has almost never proven to be the actual case, it is just the standard "pat" answer that all developers give because they do not want ANY limitations put on them. There is almost never any regard given to Best Practice and Enterprise Standards for security and configuration creep by developers. They tend to download whatever they feel like downloading onto production servers. Surprisingly, I have know very few developers that "prefer" to operate in a defined, locked-down, and structured change management system. Most developers I have dealt with do not draw much distinction between a dev environment and a prod environment. They tend to do whatever is convenient for them and create absolute chaos and security issues. This, of course, does not apply universally, but it has been the case with most developers I have worked with in my 20 years of engineering experience. Most developers love to operate with autonomy and as if they are in a small mom and pop environment. Only the true development professionals that I have worked with understand how structure helps them and the enterprise, rather than viewing "rules" as an enemy in the way of their ability to get the job done. Giving local admin rights on production servers is the lazy way to accomplish what needs to get done. Developers need to understand that it is the Engineers and Admins duty to protect the enterprise and maintain viable recovery point objectives. In a true enterprise, It should not be the wild west, where the developers are the gunslingers doing whatever they please.