Re: Performance Trap - Opening/Closing Files Inside a Loop

[xorl]

Now this is a perfect example of the classic setup. The Java guy did not give you enough information before you began the project. Now the boss is going to be told that perl is old and too slow. You'll be seeing a memo soon saying that all perl programs will need to be converted to Java and that all perl programmers will need to either learn Java or be fired. You better strike now. Have a meeting with the boss. Explain the problem have a working demo of your revised code that shows how much faster it is now that you have enough information. Good Luck.

[Limbic~Region]

xorl,
I left out the office politics. This isn't about Java versus Perl in the workplace though it very much might be for this one developer. Read my reply here for more information. While it isn't my job to write code (at least not on a day to day basis), I do try and help out the contractors when I can. In this particular case, my help was only wanted if the problem was insignificant.

[xorl]

Ah then you might be safe. But I don't think so.

The more jobs I have, the more I realize with very few exceptions there is always some kind of office politics motivating most people's actions at work (and sometimes even outside of work). This has proven to be the case in the small companies (3-10 employees) to the large companies (4,000-10,000 employees) and all the sizes in between.

I would still wonder why they'd ask you (the guy with the non-programming title) to solve a "simple" task with an "inferior" language. It could just be the contractor wants to show in his own mind that your company needs him, or it could be something more complex. I'd dig a little deeper and watch out for any rumors.

Again Good Luck.

On the bright side, your question has helped me fix a problem I was having. Thanks!