Hostile development

Question

Well, not so hostile. I am curious to find out how people are developing in large corporate networks that define all kinds of unfriendly services and policies of the developer on desktops (I think ProQuota, overly zealous anti-virus scanners, no local administrator, no access to SO). I previously used virtual LANs that were used efficiently or completely shared parallel networks, but they are not always practical. Any other tips?

Answer 1

The most important thing (if possible) is to gain support from your boss.

If he is not a PHB, he will often understand the effect of these restrictions on you, your team, and indirectly on his success. If the requests are reasonable, it can provide a buffer if you go against IT. In addition, if the whole team or other developers are looking for the same policies, this “ability to negotiate with groups" can be used to create custom policies.

, . , -, , . , (, ), ​​ , . , -, , , .

( , ), , , , , . , , , .

Answer 2

, , - , - , , 300 , .

Answer 3

, , .

:

• 4 , . 5 , .
• - . x, y z . - , , .

.

Answer 4

() , - , .

- -, " ", , - 't , .

Answer 5

/ sys, , ​​(-), , /job .

, , , , , - ( ), .

2

Answer 6

. . , , .

Answer 7

.

Answer 8

, ( , ).

, . Visio USB-.

USB, . OWA .

Answer 9

, . , , , , , , .

SO, .

Answer 10

, , , 2- , .

I finally found a solution. MSVC 6 has an integrated debugger. I went into the task manager and selected the mcaffee scanner process, and told it to debug. This started msvc6 and the scanner froze at the breakpoint. I hit reset and the problem went away. After about 6 months, they removed the policy, and everything was fine.