As did SCCS, RCS, CVS, and SVN ...
Build systems and source control systems are shit work that are in the way of doing what I need to do. Basing interview questions on that is absurd.
As did SCCS, RCS, CVS, and SVN ...
Build systems and source control systems are shit work that are in the way of doing what I need to do. Basing interview questions on that is absurd.
If they had a good explanation for that gap in knowledge, like working for the past 20 years somewhere that was stuck in legacy code and running on SVN, I'd definitely take that into consideration. I might still want to be certain this candidate is smart enough to quickly pivot into a new codebase and new tools. I've met many people who struggle with exactly that kind of change which is exactly why they don't keep their knowledge current.
I'll admit that asking people how git works isn't a question I would ask in an interview. Playing devil's advocate though, I would probably not hire someone claiming to be a senior developer who doesn't know how git works.
I use Git only because other people force me to use Git. Otherwise, I use something better.
Also Git and Mercurial are about the same age and less than 20 years old. Perforce is far older than both of them.