You're dramatizing other people's statements quite a bit. Nobody is saying that the use of Git should be the subject of lectures, unless you're using Git's sour

You're dramatizing other people's statements quite a bit. Nobody is saying that the use of Git should be the subject of lectures, unless you're using Git's source code or software design to exemplify some technical points. But grade based on projects and require the use of these tools - e.g. Git, GitHub, Maven, and Python - to work on them. Then, as a teacher, you should know how to use them yourself because you SHOULD use them in your own development. (Even if you're doing research you should use a version control system. VCS's are practically designed for the scientific method.) Again, let's keep in mind the premise: CS and SE are separate departments in a uni. Professors who gravitate more toward forwarding computational science are in CS; professors who gravitate more toward the science of building software systems are in SE. I posit that such a division would put people where they belong and make people going for SE better prepared.