4 ms·
I talked to a number of seniors majoring in computer science at a decent college not long ago - none of them knew what software version control was. While, or
by Ologn 10y ago
I talked to a number of seniors majoring in computer science at a decent college not long ago - none of them knew what software version control was.
While, or right after, taking these theoretical courses in Java or graphics or whatnot, I would launch a project in that area to ground all that theory in something I could then manifest. I don't think this occurred to many of them, but to be fair, they are young and have been in school all their lives, and I went to class with a lot of (mostly non-programming) experience in the IT business already under my belt.
- timdev2 10y ago> none of them knew what software version control was. I was pretty intimately familiar with CVS by the time I graduated (very late in the 90s). But now that I think about it, it was probably introduced in an "Intro to C and Unix" which was a 1-credit class one of the faculty forced as a pre-req for certain higher-level courses like those on compilers. It was a crash-course on C (for students who had mainly used Pascal in their first year or two), Unix philosophy, and some associated tools (make, cvs, vi/emacs). It only met the first third of the semester, so it could be taken concurrently with the class the required it. I wonder if other schools do something similar. It worked quite well, since by the the time you got up to speed, it was time to start building lexers in the compilers course.
- flukus 10y agoMost developers (senior ones too) I come across only know the very basics of version control, how to check in/out and branch, but not merge.