Return to Answer

First, If it's a good question we will migrate it to the correct place. It will only be closed if it's a poor question. We do not delete questions (unless it's not even vaguely a question).

It's pretty common for Devs to be Admins of their own computers for the reasons you've listed. See the related questions:

• Should dev be admin on their computer?
• Is locking down a developers machine more effort than its worth?
• How to assign enough perms to a dev without full Admin rights
• Windows Permissions for Developers?

Also, on Programmers.SO:

• https://softwareengineering.stackexchange.com/questions/62207/windows-permissions-for-developers
• https://softwareengineering.stackexchange.com/questions/4596/is-local-user-rights-enough-or-do-developers-need-local-administrator-or-power

There's also quite a bit of discussion about the Devs not being Admins over their Workstation, but are Admins over VMs they can run on their workstation or on a development server/cluster. This allows a level of abstraction where the Devs aren't admins over any physical boxes, but have rights over the more easily managed (aka Wiped/Reinstalled) VMs to do their development dirty work.

First, If it's a good question we will migrate it to the correct place. It will only be closed if it's a poor question. We do not delete questions (unless it's not even vaguely a question).

It's pretty common for Devs to be Admins of their own computers for the reasons you've listed. See the related questions:

• Should dev be admin on their computer?
• Is locking down a developers machine more effort than its worth?
• How to assign enough perms to a dev without full Admin rights
• Windows Permissions for Developers?

Also, on Programmers.SO:

• https://softwareengineering.stackexchange.com/questions/62207/windows-permissions-for-developers
• https://softwareengineering.stackexchange.com/questions/4596/is-local-user-rights-enough-or-do-developers-need-local-administrator-or-power

There's also quite a bit of discussion about the Devs not being Admins over their Workstation, but are Admins over VMs they can run on their workstation or on a development server/cluster. This allows a level of abstraction where the Devs aren't admins over any physical boxes, but have rights over the more easily managed (aka Wiped/Reinstalled) VMs to do their development dirty work.

First, If it's a good question we will migrate it to the correct place. It will only be closed if it's a poor question. We do not delete questions (unless it's not even vaguely a question).

It's pretty common for Devs to be Admins of their own computers for the reasons you've listed. See the related questions:

• Should dev be admin on their computer?
• Is locking down a developers machine more effort than its worth?
• How to assign enough perms to a dev without full Admin rights
• Windows Permissions for Developers?

Also, on Programmers.SO:

• http://programmers.stackexchange.com/questions/62207/windows-permissions-for-developers
• http://programmers.stackexchange.com/questions/4596/is-local-user-rights-enough-or-do-developers-need-local-administrator-or-power

There's also quite a bit of discussion about the Devs not being Admins over their Workstation, but are Admins over VMs they can run on their workstation or on a development server/cluster. This allows a level of abstraction where the Devs aren't admins over any physical boxes, but have rights over the more easily managed (aka Wiped/Reinstalled) VMs to do their development dirty work.

First, If it's a good question we will migrate it to the correct place. It will only be closed if it's a poor question. We do not delete questions (unless it's not even vaguely a question).

It's pretty common for Devs to be Admins of their own computers for the reasons you've listed. See the related questions:

• Should dev be admin on their computer?
• Is locking down a developers machine more effort than its worth?
• How to assign enough perms to a dev without full Admin rights
• Windows Permissions for Developers?

Also, on Programmers.SO:

• https://softwareengineering.stackexchange.com/questions/62207/windows-permissions-for-developers
• https://softwareengineering.stackexchange.com/questions/4596/is-local-user-rights-enough-or-do-developers-need-local-administrator-or-power

There's also quite a bit of discussion about the Devs not being Admins over their Workstation, but are Admins over VMs they can run on their workstation or on a development server/cluster. This allows a level of abstraction where the Devs aren't admins over any physical boxes, but have rights over the more easily managed (aka Wiped/Reinstalled) VMs to do their development dirty work.

First, If it's a good question we will migrate it to the correct place. It will only be closed if it's a poor question. We do not delete questions (unless it's not even vaguely a question).

It's pretty common for Devs to be Admins of their own computers for the reasons you've listed. See the related questions:

• Should dev be admin on their computer?
• Is locking down a developers machine more effort than its worth?
• How to assign enough perms to a dev without full Admin rights
• Windows Permissions for Developers?

First, If it's a good question we will migrate it to the correct place. It will only be closed if it's a poor question. We do not delete questions (unless it's not even vaguely a question).

It's pretty common for Devs to be Admins of their own computers for the reasons you've listed. See the related questions:

• Should dev be admin on their computer?
• Is locking down a developers machine more effort than its worth?
• How to assign enough perms to a dev without full Admin rights
• Windows Permissions for Developers?

Also, on Programmers.SO:

• http://programmers.stackexchange.com/questions/62207/windows-permissions-for-developers
• http://programmers.stackexchange.com/questions/4596/is-local-user-rights-enough-or-do-developers-need-local-administrator-or-power

There's also quite a bit of discussion about the Devs not being Admins over their Workstation, but are Admins over VMs they can run on their workstation or on a development server/cluster. This allows a level of abstraction where the Devs aren't admins over any physical boxes, but have rights over the more easily managed (aka Wiped/Reinstalled) VMs to do their development dirty work.