On Fri, 11 Jan 2008 12:45:59 -0700, Howard Brazee <[EMAIL PROTECTED]> wrote:
>... >It depends on what the craft of the programming is supposed to be. The >reason for making efficient code is to save the company money. If the >programmer turned some of his attention towards understanding the >users' needs better, his value to the company can be improved. >... The original article said "software engineer", not "programer". It wasn't explicitly stated, but I think that implies some element of design, not just implementing. While that might include picking the best existing solution it also includes creating a new solution if the "best" is not "good". And that implies being able to evaluate the existing collection of existing solutions, not just be able to pick one off the shelf. Pat O'Keefe ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
