Go over the whole programming life cycle, including what happens to your code after you're done with it.
- Pre-planning stages, and a bit on how to look for an existing project/existing code you can use to reduce the amount of original code
- A small (Basic) overview of licenses and how that external code affects what licenses you can and can't use (and other considerations that go into licensing)
- Concurrent version control, and versioning. I'd do SVN/Git, but to each his own. You will save them SO MUCH time if you introduce it to them now rather than learning on the job.
- Show them what avenues there are for open-sourcing code (Google Code, Github, etc.) and when/how to tell if it's appropriate or not.
None of this is C-specific, but I add it because I personally just went through the 'C for Electrical Engineers' at my university, and this is all stuff I had to find out on my own.
