Alexander: add see also and properly place references

2023-02-18T05:54:40Z

add see also and properly place references

← Older revision		Revision as of 05:54, 18 February 2023
Line 11:		Line 11:
	In the context of computing and software architecture, the kitchen sink is an extreme end state of poor architecture. Ordinarily, programmers attempt to avoid this by practising such things as [[modular programming]], but in effect this does not avoid the problem of scope creep so much as it compartmentalises it, making the project at hand into a bureaucratic object, and leading to massive inefficiencies.		In the context of computing and software architecture, the kitchen sink is an extreme end state of poor architecture. Ordinarily, programmers attempt to avoid this by practising such things as [[modular programming]], but in effect this does not avoid the problem of scope creep so much as it compartmentalises it, making the project at hand into a bureaucratic object, and leading to massive inefficiencies.

	~~{{mission/software architecture}}~~		==See also==
			* [[Cool targets don't move]]

	==References==		==References==
			<references/>

			{{mission/software architecture}}

Alexander: Created page with "The '''kitchen sink''' is a metaphor referring to the property of software to exhibit an unbounded scope or feature creep. It most commonly afflicts projects whose maintainers aim to be "jacks of all trades", such as many popular programming languages. ==Etymological evidence== The concept has probably existed for decades, even as long as programming has been a thing as the idiom "everything but the kitchen sink", but we can definitively date it to at least 2011 via [//..."

2023-02-18T00:58:30Z

Created page with "The '''kitchen sink''' is a metaphor referring to the property of software to exhibit an unbounded scope or feature creep. It most commonly afflicts projects whose maintainers aim to be "jacks of all trades", such as many popular programming languages. ==Etymological evidence== The concept has probably existed for decades, even as long as programming has been a thing as the idiom "everything but the kitchen sink", but we can definitively date it to at least 2011 via [//..."

New page

The '''kitchen sink''' is a metaphor referring to the property of software to exhibit an unbounded scope or feature creep. It most commonly afflicts projects whose maintainers aim to be "jacks of all trades", such as many popular programming languages.

==Etymological evidence==
The concept has probably existed for decades, even as long as programming has been a thing as the idiom "everything but the kitchen sink", but we can definitively date it to at least 2011 via [//archive.ph/fihI6 this] Hacker News post:

<blockquote>Scala seems to be the academic kitchen sink of programming languages.</blockquote>

There are other instances confirming this as a concept in the world of software.<ref>Scala is a kitchen sink language […]. Hacker News. December 31, 2018. Retrieved on February 17, 2023. [//archive.ph/9MfBh Archive.]</ref><ref>What is a "kitchen sink" language?. Quora. Unknown date, approx. 2 years prior to retrieval. Retrieved on February 17, 2023. [//archive.ph/2tCwq Archive.]</ref> It is also a well-known concept in the world of "conlangs", as discussed [//archive.ph/J8VbV on Reddit] and [//archive.ph/whAYy on the FrathWiki].

==Issues==
In the context of computing and software architecture, the kitchen sink is an extreme end state of poor architecture. Ordinarily, programmers attempt to avoid this by practising such things as [[modular programming]], but in effect this does not avoid the problem of scope creep so much as it compartmentalises it, making the project at hand into a bureaucratic object, and leading to massive inefficiencies.

{{mission/software architecture}}

==References==

Kitchen sink - Revision history

Alexander: add see also and properly place references