Re: (dws)Re^2: On Leaving a Script Behind

The other benefit of leaving work stuff behind is that if I ever write the script again, the result is generally better.

What happens if you use a bit of code that's identical to part of the original? If you came up with a great method of doing something, does that mean that you'll have to deliberately code it badly if you ever rewrite the script at another employer?

Comment on Re: (dws)Re^2: On Leaving a Script Behind

Replies are listed 'Best First'.
Re^2: (dws)Re^2: On Leaving a Script Behind by dws (Chancellor) on Jun 10, 2001 at 01:31 UTC
What happens if you use a bit of code that's identical to part of the original? If you came up with a great method of doing something, does that mean that you'll have to deliberately code it badly if you ever rewrite the script at another employer? I never deliberately write bad code, unless I'm writing down an example of how not to do things. If what comes out of my finger tips the second time around looks alot like the initial effort, that's either an indication that the first attempt was good, or an indication that I haven't learning anything in the meantime. It's often hard to know which of those is true.	[reply]

Replies are listed 'Best First'.

Re^2: (dws)Re^2: On Leaving a Script Behind
by dws (Chancellor) on Jun 10, 2001 at 01:31 UTC

I never deliberately write bad code, unless I'm writing down an example of how not to do things.

If what comes out of my finger tips the second time around looks alot like the initial effort, that's either an indication that the first attempt was good, or an indication that I haven't learning anything in the meantime. It's often hard to know which of those is true.

[reply]