Hello Gabor,
You may want to add the following:
If there is legacy code - it is maintainable (well-structured and
well-documented).
--- Omer
On Sun, 2010-05-09 at 05:41 +0300, Gabor Szabo wrote:
> guy,
>
> thanks for the quick reply at this early hour of the day
>
> On Sun, May 9, 2010 at 5:28 AM, guy keren <[email protected]> wrote:
> >
> > gabor - i think you (and most of the community) missed a major factor -
> > the job should be interesting/challenging/rewarding, and the system
> > being developed should be interesting/challenging/rewarding.
>
> I am not sure on what do you base your generalization about "most of
> the community"
> but I added your answer
> "The system being developed should be interesting/challenging/rewarding"
> to the potential answers as I think this is good one that I missed out.
--
Philip Machanick: "caution: if you write code like this, immediately
after you are fired the person assigned to maintaining your code after
you leave will resign"
My own blog is at http://www.zak.co.il/tddpirate/
My opinions, as expressed in this E-mail message, are mine alone.
They do not represent the official policy of any organization with which
I may be affiliated in any way.
WARNING TO SPAMMERS: at http://www.zak.co.il/spamwarning.html
_______________________________________________
Perl mailing list
[email protected]
http://mail.perl.org.il/mailman/listinfo/perl
