in reply to Production Environments and "Foreign" Code

I find this a totally bizarre requirement/policy.

Is it only Perl programmers who labour under these ridiculous restrictions or everybody?

How on earth would Java or C++ or Delphi programmers function without "foreign" code?

The whole idea is ludicrous.

Helgi Briem
helgi AT decode DOT is

  • Comment on Re: Production Environments and "Foreign" Code

Replies are listed 'Best First'.
Re: Re: Production Environments and "Foreign" Code
by michaeld (Monk) on Mar 13, 2003 at 21:20 UTC

    I think we all bump into these kind of restrictions some time.

    But... there's no need to despair just yet!...I seem to remember that not long ago, Java was looked upon as "weird-stuff-never-to-be-touched-by-a-decent-IT-person". (In our company anyway...)

    And look where Java ended up today!

    It's just a matter of time and patience...


Re: Re: Production Environments and "Foreign" Code
by Anonymous Monk on Mar 14, 2003 at 12:31 UTC
    The snide answer is that only Perl programmers are productive enough to be able to rewrite the foreign code and still get their work done.

    But the truth is that there are many who have helped major projects crash and burn by re-inventing the wheel. Check out Crash And Burn Java for instance, among its tips is re-invent your infrastructure so that you can use up some programming talent and then have something else to sell afterwards. (That rant is, I understand, based on an actual project.)