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 12:09:55 +1000
"Doc" wrote:
> In other words, successful compilation, successful operation, and
> efficiency are required for code or any other solution to be
> considered "elegant".
This is consistent with my knowledge of how the
term "elegant" is used in technical and scientific
contexts. It seems impossible to think of a scientist
applying the term "elegant" to a solution that has been
proved wrong (except perhaps in irony) -- just as it
seems impossible to think of "elegant" code that won't
compile.
I see an interesting parallel here with the recurring threads
regarding "good writing" that is "technically inaccurate."
How can it be "good" in any important sense if it wrong
or misleading? Only if you omit "fitness for purpose" from
criteria for "good" or "elegant" can you arrive at such a
twisted conclusion.
--
Michael West
Melbourne, Australia
---
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.