in reply to Re: Re: On Leaving a Script Behind
in thread On Leaving a Script Behind

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-.

Replies are listed 'Best First'.
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