in reply to Re: Perl contract problems in thread Perl contract problems
I agree. If they're paying you to do something, you basically do it, or you don't get paid. You don't own the code, the company you're contracting for does -- if they want it a certain way, you're pretty much obligated to make it that way. If the boss wants code that has every line documented, and you refuse, I can bet he won't be keeping you around for too long (as unfortunate as this particular situation is).
scott.
Re: Re: Re: Perl contract problems
by diotalevi (Canon) on Sep 26, 2002 at 15:52 UTC
|
I think these points are missing an important point that as a programmer it is part of your professional obligation to help create the requirements that you'll be working under to ensure that they are do able, make sense and will benefit your client. The way the original poster worded things it sounded as if things were completely out of his control. Obviously that's not true in any reasonable situation - I you were my teammate then I'd expect you to push back on things that don't make sense and help to guide things appropriately. Things still can still go badly but at least you'll have exercised your obligation to do a good job which is a larger issue than just having good code.
| [reply] |
|