- The following discussion is an archived debate of the proposed deletion of the article below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.
The result was soft delete. Based on minimal participation, this uncontroversial nomination is treated as a soft deletion. Editors can request the article's undeletion for any reason. Spartaz Humbug! 06:00, 20 May 2026 (UTC)
- Comment-driven development (edit | talk | history | protect | delete | links | watch | logs | views) – (View log | edits since nomination)
- (Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)
Only cited to blogs. Fails WP:GNG, contested PROD. Only WP:RS that doesn't fail WP:SIGCOV I could find was a paywalled O'Reilly video.
On the talk page, this source was found:
Ousterhout, John (July 2021). A Philosophy Of Software Design (Second Edition (v2.0) ed.). Palo Alto, CA.: Yaknyam Press. pp. Chapter 15. ISBN 978-1-7321022-2-4.
Unfortunately even with those two sources, it still fails WP:GNG. ozmoozmo@enwiki$t.c 06:03, 28 April 2026 (UTC)
- Could you please explain why? Exactly, which point is violated in your opinion?
I think that papers by John Ousterhout from Stanford University are a very reliable source of information. --Mi.Fe (talk) 10:11, 29 April 2026 (UTC)
- What paper? Please provide a link. ozmoozmo@enwiki$t.c 01:34, 30 April 2026 (UTC)
Relisted to generate a more thorough discussion and clearer consensus.Please add new comments below this notice. Thanks, Cavarrone 04:58, 5 May 2026 (UTC) Relisted to generate a more thorough discussion and clearer consensus.Please add new comments below this notice. Thanks, BhikhariInformer (talk) 17:55, 12 May 2026 (UTC)
- Comment - for what it's worth, I have worked in software development for roughly 20 years and have never heard this practice earnestly described as a development methodology similar to e.g. test-driven development. What's described in the article sounds like a combination of several development techniques which are so common and obvious that they hardly even have names, e.g. writing design documents before coding, or using code comments to document design decisions. It doesn't help that the "X-driven development" snowclone is often used as a joke, cf. meme-driven development, beer-driven development, pain-driven development, etc - and I suspect that some of the references on this article may be a bit tongue-in-cheek themselves. Omphalographer (talk) 22:09, 12 May 2026 (UTC)
- The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.