Re:Empirical Evidence for the Value of Version Control?
by brudgers on Monday December 17, 2012 @09:30AM
(#4932355)
"but I have no experimental evidence to base that decision."
"Empirical" and "experimental" are not synonyms. Experimental evidence constitutes a small range within the set of all things which might count as empirical evidence - e.g. anecdotes are empirical evidence but not experimental evidence.
It is rare for something as vague as version control to undergo formal investigation via experiment. As this thread shows, there is a broad range of often incompatible activities which might be called "version control."
Typically, investigations would be via trial (and error), not experiment. The experience gained from such trials is empirical evidence - evidence from experience is all that "empirical" means.
Although the strength of experimental evidence is typically based upon statistical correlation, the strength of empirical evidence is based on various other types of judgements.
It would not be unreasonable to give the reference to Moore substantial empirical weight, if one attributed significant authority to Moore (perhaps based upon previously finding that Moore's judgement about similar matters corresponded with one's own experience). On the other hand, such an appeal to authority would never be acceptable within an experiment.
In a sense, the idea of experimenting with version control, in a formal sense is a bit absurd - at the point where the benefits or disadvantages appear obvious, the experiment would be abandoned, e.g. at the point where productivity rises sharply or the shipping date is missed.
In a sense, the question seems to miscategorize version control as something other than a tool. Tools are particular. So is version control. There are some programming tasks where it is hammer to nails. Other tasks however, use screws.
Version control, as others in this thread have noted, is not a monolithic thing. It's a cluster concept. Implementations may be hammers, screwdrivers, rivet guns, or glue.
"Empirical" and "experimental" are not synonyms. Experimental evidence constitutes a small range within the set of all things which might count as empirical evidence - e.g. anecdotes are empirical evidence but not experimental evidence.
It is rare for something as vague as version control to undergo formal investigation via experiment. As this thread shows, there is a broad range of often incompatible activities which might be called "version control."
Typically, investigations would be via trial (and error), not experiment. The experience gained from such trials is empirical evidence - evidence from experience is all that "empirical" means.
Although the strength of experimental evidence is typically based upon statistical correlation, the strength of empirical evidence is based on various other types of judgements.
It would not be unreasonable to give the reference to Moore substantial empirical weight, if one attributed significant authority to Moore (perhaps based upon previously finding that Moore's judgement about similar matters corresponded with one's own experience). On the other hand, such an appeal to authority would never be acceptable within an experiment.
In a sense, the idea of experimenting with version control, in a formal sense is a bit absurd - at the point where the benefits or disadvantages appear obvious, the experiment would be abandoned, e.g. at the point where productivity rises sharply or the shipping date is missed.
In a sense, the question seems to miscategorize version control as something other than a tool. Tools are particular. So is version control. There are some programming tasks where it is hammer to nails. Other tasks however, use screws.
Version control, as others in this thread have noted, is not a monolithic thing. It's a cluster concept. Implementations may be hammers, screwdrivers, rivet guns, or glue.