Re: Re: On Leaving a Script Behind

That sounds like a pretty hazy area. Most likely, you could do it, and get away with it, but if some higher-up were to find out about it, things could get hairy. It is, after all, their property (depending of course on what sort of agreement you have with your employer).

I also know that some of the scripts that I've written at work could be seen as containing sensitive information; something that might be useful to a competitor or whatnot. Another mess that you just don't want to get into.

Comment on Re: Re: On Leaving a Script Behind

Replies are listed 'Best First'.
Re: Re: Re: On Leaving a Script Behind by cacharbe (Curate) on Jun 08, 2001 at 17:31 UTC
Granted. I know what kind of situation I'm in here. My question really goes to people's opinions on the topic as a whole. Should we be ensuring that we can take our work and learning with us? If for nothing more than the processes we've learned? If I come up with a faster sort algorithm that is being used for high-speed data collection, does that mean I shouldn't be able to use it at my next job? Many of us sign non-competition agreements anyway, so it's not like we're going to the nearest competitor, getting a job and doing a core dump. If we are, then that's another ball of twine... Thoughts? C-.	[reply]
When You Don't Have to Leave a Script Behind by da (Friar) on Jun 09, 2001 at 02:04 UTC
Another way around the problem: I recently contracted on a project with a lead developer who was open-source-friendly, so during our first spec discussion, I asked if I could contribute my work to CPAN when we were finished. He thought it was a great idea, and it helped me decide to take the contract. `___` `-DA`	[reply] [d/l] [select]