Hello! I'm running an Ideological Turing Test for my local rationality group, and I'm wondering what ideology to use (and what prompts to use for that ideology). Palladias has previously run a number of tests on Christianity, but ideally I'd find something that was a good 50/50 split for my community, and I don't expect to find many Christians in my local group. The original test was proposed for politics, which seems like a reasonable first-guess, but I also worry that my group has too many liberals and not enough conservatives to make that work well.
What I plan to do is email the participants who have agreed to write entries asking how they stand on a number of issues (politics, religion, etc) and then use the issue that is most divisive within the population. To do that, however, I'll need a number of possible issues. Do any of you have good ideas for ITT domains other than religion or politics, particularly for rationalists?
(Side questions:
I've been leaning towards using the name "Caplan Test" instead of "Ideological Turing Test". I think the current name is too unwieldy and gives the wrong impression. Does the ITT name seem worth keeping?
Also, would anyone on here be interested in submitting entries to my test and/or seeing results?)
In my view, svn has a number of benefits over git. Let me offer a quick runthrough of why I prefer svn for small projects.
The main reason to use svn in my view is simplicity. git can't do many things svn does with as little friction as svn requires.
Centralized version control is definitely simpler than distributed. Distributed can be useful if you want to develop a feature offline (and find the svn ways of doing that to be a pain, as I do), want to work on something independently for a while, want to work on an experimental branch, etc.. But there's a good reason to prefer centralized in some cases. Distributed version control is too confusing for many people you might want to collaborate with. My research group has enough trouble getting my PhD advisor to use svn. Do you think this will be easier with git?
The documentation for git is pretty bad. In contrast to svn, I can't rely on the documentation for git making sense and basically have to Google for many things, even some things which are straightforward in svn (like svn keywords). The Pro Git website is pretty good, however.
One thing I like is having a incrementing number that refers to a unique version. You actually can get that in git, but it's a complicated command that I've never seen used in real life. This is just how svn works.
Let's say you are using git just want to print the hash and date of last modification in your code or document. svn has a keyword functionality to do this automatically when you update. git makes this at least moderately complicated (for silly reasons). There are several ways to do this, but editing the file directly with a script is unsatisfactory because the file will show up modified, unless there's some git way around this. In svn the files show up as unmodified. You also could pass in the hash at compile time, which is just extra work over svn.
I have heard conflicting things about partial checkouts in git. My impression is that they work but are more complicated than svn. Partial checkouts are totally normal and easy in svn. I do them fairly regularly, as well.
GUIs for git were still underdeveloped last I checked, or at least the free ones were. GUIs make a number of things much easier. At one point I started converting my repositories over to git because I wanted to work offline more often, but the lack of good GUIs made me stick with svn. (I have some other restrictions here that made some GUIs not attractive, and maybe I should look into this again.)
Here are the advantages I see to git/github: pull requests being code reviews and the distributed nature of the software. The former is great, as problems are caught early. The latter is not always an advantage, as I explained earlier, but generally is a major advantage in large projects.
To be honest, I could see myself changing my mind over this in the future, but for now I see no reason to switch from svn to git for most of the repositories I have.
The big thing (for some people) that you are missing with git is that it makes working with branches really easy. In my first job we used SVN and maintaining separate branches was a pain in the ass, to the point where we only did it for a release branch, while with git it's pretty trivial to the point where people use them all the time even when working locally only.
I do agree that git's documentation and UX for basic operations is not as nice as SVN.
edit: Also agree about the signalling part to some extent. I do feel like there's a tendency among some programmers to gravitate toward the most complex plausible technology in order to show how smart they are.