Creeping elegance
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. The article may be deleted if this message remains in place for seven days, i.e., after 03:38, 30 August 2024 (UTC). Find sources: "Creeping elegance" – news · newspapers · books · scholar · JSTOR Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Creeping elegance|concern=Fails [[WP:N]]. Googling suggests this is not so much a practical concept as a hypothetical one, the inverse of legacy code bloat. Available sources often devolve into confusion about whether this is synonymous with [[feature creep]], as the article itself appears to do. To boot it is written in unusually unencyclopedic language. Google News returns nothing relevant, nor does the News Archive. Google Books returns a few hits, but nothing that exactly matches the concept as here described. I think the lack of activity on such a luridly-written page over the past 20 years kind of speaks for itself.}} ~~~~ |
This article needs additional citations for verification. (February 2024) |
In software development, creeping elegance, related to creeping featurism and second-system effect, is the tendency of programmers to disproportionately emphasize elegance in software at the expense of other requirements such as functionality, shipping schedule, and usability.
Creeping elegance is also forced by customers and sales personnel in the last stages of software development. Often one comes up with "just another feature" before the delivery date,[1]: 81 and the software developer is left with the choice of prioritizing between delivery on time according to schedule or to fully satisfy customers and/or the sales department.
Complexity and readability are the main reasons why programmers tend to favor elegance over functionality all else being equal, simply to mitigate the more marginal cognitive burden of the task, which is very high compared to many other fields even in computer science.
It is definitely an area in which management and marketing conflict a lot with programmers, but most programmers will behave very petulantly when asked to deal with very old, poorly documented, or otherwise poor code, and often this will lead to easter eggs, intentional exploit vulnerabilities, and staff turnover.
References
[edit]- ^ Kessler, Eric H. (2000). "Tightening the belt: methods for reducing development costs associated with new product innovation". Journal of Engineering and Technology Management. 17 (1): 59–92. doi:10.1016/S0923-4748(99)00020-X. ISSN 0923-4748. Retrieved February 15, 2023.
External links
[edit]