Developers vs. virus scanners
In the "two data points make a trend" department, both the company I'm leaving and the one I'm joining are currently in the middle of lively and sometimes hilarious discussions chronicling the continuing problem of developers fighting with virus scanners for cpu and disk cycles as well as basic permission to do things like send mail.
Now that I'm leaving Openwave, I can freely admit that for most of my tenure at the company I've subversively disabled my virus scanner, not by removing it (too easy to detect, IT is on to that) but by binary-editing one or two of the key DLLs to ensure that they never load correctly. The penalty of living with these things has never been justified, in my opinion. Keeping a sharp eye on what processes are running and analyzing an occasional 3 or 4 hour Ethereal capture by hand turns out to waste a lot less of my time.
Nevertheless, as a responsible and upstanding engineering manager I'm probably not supposed to recommend this method, so if anyone has actually *solved* this problem before I'd really like to hear about it.
Now that I'm leaving Openwave, I can freely admit that for most of my tenure at the company I've subversively disabled my virus scanner, not by removing it (too easy to detect, IT is on to that) but by binary-editing one or two of the key DLLs to ensure that they never load correctly. The penalty of living with these things has never been justified, in my opinion. Keeping a sharp eye on what processes are running and analyzing an occasional 3 or 4 hour Ethereal capture by hand turns out to waste a lot less of my time.
Nevertheless, as a responsible and upstanding engineering manager I'm probably not supposed to recommend this method, so if anyone has actually *solved* this problem before I'd really like to hear about it.