1. What's LD50 [1] for version control, i.e., how long would people have to use it (or watch someone else use) for half of them to be convinced it's worth adopting? I think LD50 for the Unix shell is less than an hour, because that's how long it takes us to introduce pipes and loops, which most workshop participants find compelling. At what point do at least half of workshop participants find Git compelling enough to actually adopt it?
In my case, about 30 seconds after I tell them that they will be assessed on the code in their last git commit prior to the submission deadline (or a tagged commit detailed in their report) :) Actually the compelling argument is the lose/restore, or the commit/retrieve elsewhere/sync with colleagues. 2. What should we say to someone like Arjun? It's clear from his post that he knows the arguments in favor of version control, and has actually tried it. It's also clear that he cares about doing things well - what can we do to convince someone like that? It's always too much trouble until just after you needed it most. _______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org The University of Dundee is a registered Scottish Charity, No: SC015096 _______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
