3 ms·
>That's equivalent to saying that a scientific claim doesn't have to be falsifiable No it isn't. Simply stating the opposite of reality doesn't make it so. >
by papsosouid 13y ago
>That's equivalent to saying that a scientific claim doesn't have to be falsifiable
No it isn't. Simply stating the opposite of reality doesn't make it so.
>It wasn't proven, because there wasn't enough evidence for a statistically relevant result until March 2013.
That is up to interpretation. Many felt there was enough evidence. This is not a case like that, there is literally no evidence at all for TDD. None. And you are demanding that I prove it doesn't have benefits. Prove programming while wearing pink socks doesn't have benefits.
>I still haven't seen the evidence to support your conclusion.
That is your fault, not mine.
>TDD's claimed benefits are falsifiable
And have been falsified, like in the link I provided you. But TDD salesmen use that falsification as evidence supporting it.
- davidcuddeback 13y agoYou're contradicting yourself: > there is literally no evidence at all for TDD > And have been falsified Falsification requires evidence. You can't say there's no evidence and then turn around to draw a conclusion two seconds later. > like in the link I provided you That is but one blog post. Science doesn't work by cherry-picking results. That's a tactic used by climate change deniers and homoeopathic medicine supporters. The evidence must be taken in full. In addition, I skimmed the paper cited in that article [1]. It appears to be measuring TDD's effects on external quality. That is not a purported benefit of TDD. Most of the research I've seen agrees with that paper: TDD doesn't improve external quality (defined by passing acceptance tests). The contention is over whether it improves internal quality. Also note that the paper cites "process conformance" as a threat to validity, which is what I've been saying is one of the major problems with TDD research all along [2]. The experiment also used students, which is known to be a problem when generalizing results. With TDD in particular, some research indicates that it's more effective with mature developers and ineffective with inexperienced developers. If you've read the rest of the research instead of cherry-picking, you would have known that. I'm not trying to make a bold claim about TDD. The evidence doesn't support that. I'm trying to help people like you look at the subject objectively. You can't form an objective opinion without evidence (which you claim) or while cherry-picking evidence (which you've done). But frankly, I don't think you want my help, so the last word is yours if you want it. [1] https://ieeexplore.ieee.org/application/mdl/mdlconfirmation.jsp?arnumber=1423994&icp=false https://ieeexplore.ieee.org/application/mdl/mdlconfirmation.... [2] That was my first bullet point in my first comment on this thread: "there's little confidence that TDD was applied correctly in many of the studies."
- papsosouid 13y agoYou are trolling right? There is no evidence to support the claims made about TDD (that it helps in any way). The claim that it helps has been falsified, by people doing TDD and non-TDD and there being no difference. These things are in no way contradictory, and I am no longer able to suspend disbelief and pretend you are actually trying to make a good-faith attempt at a real conversation here.