TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Term for elegant, efficient, tight code? From:"Michael West" <mbwest -at- removebigpond -dot- net -dot- au> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Sun, 1 Jun 2003 19:57:19 +1000
<dmbrown -at- brown-inc -dot- com> wrote in message news:200561 -at- techwr-l -dot- -dot- -dot-
>
> Doc wrote:
> >
> > In other words, successful compilation, successful operation, and
> > efficiency are required for code or any other solution to be
> > considered "elegant".
>
> Compilation is trivial; operation is hardly more difficult--both are a given, and
it's pointless to include them in the discussion. According to this definition, that
leaves efficiency, which is not alone enough to be described as elegance.
Doc didn't say they were sufficient -- he said they
were necessary.
Whether something is or isn't a "given" is something that
requires logical argument, not just bald assertion.
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.