Beefy Boxes and Bandwidth Generously Provided by pair Networks Bob
Problems? Is your data what you think it is?
 
PerlMonks  

Re^4: Analyzing large Perl code base.

by kscaldef (Pilgrim)
on Apr 15, 2005 at 16:40 UTC ( #448253=note: print w/ replies, xml ) Need Help??


in reply to Re^3: Analyzing large Perl code base.
in thread Analyzing large Perl code base.

Well, that works until you go to the business and ask, "Where's the spec for feature X?" and they response, "Uh... well, what does it do now?".


Comment on Re^4: Analyzing large Perl code base.
Re^5: Analyzing large Perl code base.
by dragonchild (Archbishop) on Apr 15, 2005 at 17:26 UTC
    That's perfect - you get to write your own specs! :-)
    • Developer: What's the spec for feature X?
    • Marketing: Uhhh ... well, what does it do now?
    • Developer: It should do foo, bar, and baz.
    • Marketing: Ok, sounds good to me.
    • Developer: Do you mind if I write that up and send it to you for a signature?
    • Marketing: (worried tone) Why would you do that?
    • Developer: Just so that if I screw up, you can hold my feet to the fire.
    • Marketing: (relieved tone) Oh, ok!

    So, you then write whatever you want, Marketing signs off on it, and you go write your test suite, refactor against it, and everyone goes home.

      That may work okay for some places, particularly if your revenue stream is only loosely coupled to the code in question. Personally, the code I work on has a lot of revenue pushed through it every day, in a very quantitative manner. So, refactoring from what it does do to what it "should" do is fairly risky. What looks best to the developer isn't always best for the business, and even if a change is for the better any unexpected changes in the metrics raise flags.

      YMMV, but I think that in a organization of any significant size, it's generally a bad idea for developers to make unilateral decisions about how the product should be changed.

        . . . in a organization of any significant size, it's generally a bad idea for developers to make unilateral decisions about how the product should be changed.

        Yes, you are absolutely correct. Now, if only Marketing or the business units would get their heads out of the collective asses long enough to actually provide usable direction to us developers, we could all go home and have milk and cookies before naptime.

        I have worked at 9 different places in the past 7 years. At 5 of them, developers wrote specifications. At 2 of them, developers co-wrote specifications. So, in less than a quarter of the places I have worked at, developers received usable specs.

        I've been lucky.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://448253]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others avoiding work at the Monastery: (18)
As of 2014-04-17 13:40 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    April first is:







    Results (447 votes), past polls