Actually no. That confuses short term business objectives with quality of programming. They overlap but aren't the same thing (sometimes they conflict, even).
Good programmer is who makes the things working well *as planned* in the time-limit planned beforehand, having good results for the *business* in the end-of-the-day.
The rest doesn't matter.
Under your definition a programmer who produces absolutely sh*te code but before the deadline, that appears to do the job, is 'good'. The poor saps who have to pick up the pieces afterwards when the code can't be debugged or modified because it's held together by chewing gum would definately disagree with this assessment - I've been there and it ain't pretty.
Sometimes deadlines have to give a little in the interests of future maintainability - good managers recognise this, as they understand that long term goals (well written code, leading ultimately to shorter maintenence cycles) can sometimes trump short term goals (releasing exactly on time).
Tony _______________________________________________ Asterisk-Users mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
