Non-programming contracting - who would [generally] own scripts and tools I write?

[BlasterBates]

The main thing is don't either bring something from home and load it on to the system or vice versa without permission.

Companies have security policies and it doesn't matter if it is well meaning, the guy in the Security dept doesn't care, a breach is a breach.

I would strongly advise doing no development at home, just do it all at work and "remember it".

They will automatically take legal action if they spot a breach, and it isn't very nice when they do.

[vwdan]

The main thing is don't either bring something from home and load it on to the system or vice versa without permission.

Companies have security policies and it doesn't matter if it is well meaning, the guy in the Security dept doesn't care, a breach is a breach.

I would strongly advise doing no development at home, just do it all at work and "remember it".

They will automatically take legal action if they spot a breach, and it isn't very nice when they do.

I think you may be over estimating the kind of stuff I do - think Powershell scripts, batch files to automate hundreds of registry tweaks and things like that. I already have a collection of handy ways to get myself (and others) out of trouble, and to me, it's part of what would be expected of a deployment engineer.

It's a fair point regarding permission, though - I guess it's very case-by-case basis in regards to how they expect me to operate.

[SueEllen]

The main thing is don't either bring something from home and load it on to the system or vice versa without permission.

Companies have security policies and it doesn't matter if it is well meaning, the guy in the Security dept doesn't care, a breach is a breach.

I would strongly advise doing no development at home, just do it all at work and "remember it".

They will automatically take legal action if they spot a breach, and it isn't very nice when they do.

Some clients provide laptops and VPNs specifically for that purpose.