Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw

Re^5: Keeping, and advancing in, your job

by dragonchild (Archbishop)
on Mar 04, 2005 at 04:14 UTC ( #436448=note: print w/replies, xml ) Need Help??

in reply to Re^4: Keeping, and advancing in, your job
in thread Keeping, and advancing in, your job

Rewriting when you are assigned to a new script is one thing. Rewriting when you are assigned to a million-line application is another, especially if that application (like most applications) doesn't have a comprehensive test suite.

In addition, any change, no matter how small, has a certain risk associated with it. Larger changes have larger risks. A risk has a very clear dollar figure associated with it. It may be appropriate to leave an application in a crufty state, because of the dollar figures associated with changing it and not changing it. I work on an application that has that exact situation. It's crufty, horrible, and needs a complete rewrite. Except, that rewrite is being done by another group and I just need to keep it limping along for another year. It's one of my many tasks; I might spend 20 hours a month on it. Yes, I could rewrite it in that time, but that is wasted effort becaue the benefits to rewriting it are only gained by amortization - you spend $100 now to save $50/year over 5 years. You are still in the hole for two years and if you expect to turn the application off in a year, is it still worth it to rewrite?

Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

  • Comment on Re^5: Keeping, and advancing in, your job

Replies are listed 'Best First'.
Re^6: Keeping, and advancing in, your job
by bwelch (Curate) on Mar 04, 2005 at 20:56 UTC
    There's the difference. Given a thousand line script, I'd easily clean it up and make it work properly betting on the time saved in maintaining it. For ten-thousand line scripts, I'd question the source for having one script that long and be more hesitant to maintain it. Is that really a small script with many modules? That might be okay to maintain or it might be trouble.

    A million line system and one person maintaining it? That sounds like a job (or a nightmare) all by itself. Are there many independent modules that don't need to be changed? At best, that would be difficult.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://436448]
[1nickt]: tobyink perl -MTypes::Standard= is_Int -Mstrict -wE 'say 1 if is_Int 1.0'
[jdporter]: so that I can use the existing expand unix util. Otherwise, I'll probably use Text::Tabs.
[1nickt]: pryrt I guess I don;t really care if user 42 logs on as 42.0 ... more of an academic question at this point.
[LanX]: jdporter: open PIPE,'-|' ?
[LanX]: oh you want the result line by line?
[jdporter]: ok, LanX, then what?
[jdporter]: It doesn't have to be line by line. Just "my program" "writes" to the external prog and also/then "reads" from it.
LanX open (You are not allowed to open to a command that pipes both in and out, but see IPC::Open2, IPC::Open3, and Bidirectional Communication with Another Process in perlipc for alternatives.)
[jdporter]: IPC::Open2, I guess
[jdporter]: yes, that

How do I use this? | Other CB clients
Other Users?
Others contemplating the Monastery: (11)
As of 2017-05-24 20:29 GMT
Find Nodes?
    Voting Booth?