3 ms·
>> Oh, and I think there are some people who use version control for the text of their papers (almost certainly a proper subset of those who are for some reason
by YeGoblynQueenne 6y ago
>> Oh, and I think there are some people who use version control for the text
of their papers (almost certainly a proper subset of those who are for some
reason writing their papers in Markdown or LaTeX). Unless your paper has a lot
of math in it, I have no idea why anyone would subject themselves to this form
of torture. Let me be the one to tell you that you are no less smart or tough
if you use Google Docs. In fact, some might say you’re more smart, because you
don’t let command-line ethos/ideology get in the way of actually getting
things done… :)
I really don't understand where this is coming from. It sounds like the
reaction of someone forced to do something difficult and time-intensive for no
good reason other than because someone thinks it's "the right way", which I
can get behind. But, from what I can tell, it's just doing a "git add" and
"git commit" every once in a while. Does that really require "command-line
ethos"?
This maybe because I don't really understand how using git to track changes to
your code or text helps reproducibility. Once you have your experiment and
plotting scripts where you want them, reproducibility should be a matter of
making those scripts available to others. Before you are at that point, using
git is useful because you can un-screw mistakes caused by big changes or
changes two or three versions of your code ago. It doesn't help reproduce your
work, just organise it so you don't end up making a big, steaming mess of it.
So maybe I don't understand what the author means by "reproducibility"?
Finally, all the same points the author makes against using version control
apply to software development also, or anyway I don't see why they shouldn't
aply to software development also. Yet, an entire industry seems to agree that
version control saves butts much more than it wastes time and one would
probably be very hard pressed to convince software developers that they don't
need to use version control. So either there's something that entire industry
is getting awfully wrong, or software developers like to "torture" themselves,
or the author is missing something, maybe?
- CJefferson 6y agoGoogle docs has history of documents. Also, while I use latex and git, it is awkward for lots of reasons -- in particular git is line based, so if two people edit a comma in a paragraph, you get a conflict. (I know some people do a line per sentence, but I hate reading that).
- YeGoblynQueenne 6y agoI confess I haven't used google docs- as per another comment I prefer to not tie down my research and my code in proprietary formats, especially one living on someone else's computer (the "cloud")! About git's awkwardness, I recognise that people who are not trained as software developers may find the command line off-putting, but on the other hand having to keep track of changes to a couple dozen documents (scripts and article versions) by hand is, for me, the stuff of nightmares. This "awkwardness" pays for itself in spades when you realise that a change in a script you've written at the start of the project and haven't tested since is suddendly raising an error and you have no idea at which point it broke. This is a common thing that comes up in my projects. Git even has a special command to do this for you - "git bisect". I can't imagine the pain in the arse it would be to try and roll back maybe months of changes by hand, by copy-pasting backup files, I guess, or by making new untracked changes, until you have nothing to go back to that actually works. I've been in situations like this, like I say. Having a bedrock of committed code that I can go back to anytime I like is a time saver of epic proportions. A bit of "awkwardness" or even worse once in a while, is totally worth it. And conflicts happen for a reason. How do you merge work of two or three members of a team without something like version control? That sounds like an even worse nightmare.
- watwut 6y agoIt is not just "having to use command line". It is also that git ui is unintuitive and awkward even by command line standards. Look at Git commands for merging and conflict solving. Look at those tutorials, they are typically bonkers complicated and don't even answer basic questions beginners have. Or, try to list all changes in one file only. In addition, you are way more likely to forget to add a file. In code, this shows up as error on jenkins or somewhere, but in document it wont.
- YeGoblynQueenne 6y agoAll I can say is that I find the complexity manageable, which is obviously because I've spent enough time using the tool that it doesn't scare me. Perhaps that is the solution? Use the tool until one is comfortable with it? It seems to me the alternative is a bunch of ad-hoc, half-baked procedures that are going to cause a lot more pain down the line. Or, of course, sitting down and writing a better tool than git (or svn, mercurial, etc). Personally, that's too much hassle given that someone has already done the work and all I have to do is learn how to use the program, which is much easier and much less time consuming. In general, that's why I use other peoples' software, even when I disagree with the logic behind them and I would do a better job if I had a go at it (which is, of course, always).