As someone whose intro to programming class WAS built on Turbo C almost thirty years ago, let me tell you how it was: One day's worth of handouts told you abou

As someone whose intro to programming class WAS built on Turbo C almost thirty years ago, let me tell you how it was: One day's worth of handouts told you about the IDE. Another handout was tips for debugging, including common compiler errors and what they meant. That was it! The rest you learned in the computer cluster, with the help of your dormmate, TA, or computer cluster tutor. The course itself, from then on out, focused (quite rightly IMO) on programming concepts, structures, abstractions, and basic algorithms. The main computer clusters on campus also had a whole panoply of brochures on how to use Unix, as well as various editors/tools. They were for use by all students, not just the CS students. In short: it should not take a massive investment of class prep and time to teach students the practicalia they will need to know. Save it for the labs. Don't make a semester course out of it. Include the whole student body as your audience by publishing self-help materials for all.