Talk:Shotgun debugging
 | This article is rated Stub-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||
| ||||||||||||||
Merge Discussion
editI suggested that this article be merged into programming by permutation. The two ideas are basically the same: both describe a process of making small, undirected changes in the absence of real understanding. The article about programming by permutation has considerably more substance. Janet LN Davis 15:31, 7 May 2007 (UTC)
- This merge proposal has been on the article since May 2007. As there has been no discussion I am closing the discussion as I do not believe that there is consensus in favour of the merge. --Deadly∀ssassin 21:06, 17 July 2008 (UTC)
- Shotgun gives random scatter - permutation is systematic, can even cover all cases ... --87.194.174.252 (talk) 16:06, 13 March 2009 (UTC)
Alternate definition
editI've been using this terminology for well over two decades in regards to peppering source code with debug statements to narrow down and eventually find bugs in situations where interactive debugging isn't possible. Communications software, heavily threaded applications, and most recently Firebird SQL where we couldn't duplicate the problem anywhere but at a customers site. 6 weeks of working with the Firebird Foundation turned out 0 results. I was able to find the problem and fix it in short order (3 iterations of code) using this tactic. It really sounds to me like the jargon file was written by someone with a misconception of what programmers are doing. Just my 2 cents. Braindead0 (talk) 13:52, 25 November 2009 (UTC)
Related Content
editThe multithreading example invokes the page Unusual_software_bug, maybe consider linking and discussing the connection? — Preceding unsigned comment added by 132.66.51.127 (talk) 11:37, 3 January 2012 (UTC)
Broad topic?
editBriefly, shotgunning is not just a debugging or software technique.
Some suggest the technique is non-deductive and not time-effective, but detailed analysis can also be time-consuming. In modular systems, element swapping can be rapid, and experience or overview knowledge can direct the swapping to narrow the scope of detailed analysis.
Can/should this article be expanded to the broader usage, or is that already accomplished elsewhere that I am unaware of?
70.166.250.162 (talk) — Preceding undated comment added 21:59, 9 December 2020 (UTC)