It would not kill anyone to offer one class, just 3 credits out of the 120 in an undergraduate career, about the practice of creating software. FWIW even my CS minor (30 credits) had such a course.
The course was structured around a single group project. We were assigned to a "customer" in the department, and we were responsible for soliciting (and formalizing) requirements, developing a design, implementing it, and testing it. Revision control was not optional, and we were taught how to use it. Our grade was based upon how well we completed the task, how well we presented ourselves to the instructor and "customer", and how we were assessed by our fellow teammates.
No one suffered any loss to their theoretical background, the universe didn't explode, and everyone left the class a better programmer than before. Since a CS degree is still, rightly or wrongly, considered the sole requirement for many programming jobs, I think it was time well spent.
The course was structured around a single group project. We were assigned to a "customer" in the department, and we were responsible for soliciting (and formalizing) requirements, developing a design, implementing it, and testing it. Revision control was not optional, and we were taught how to use it. Our grade was based upon how well we completed the task, how well we presented ourselves to the instructor and "customer", and how we were assessed by our fellow teammates.
No one suffered any loss to their theoretical background, the universe didn't explode, and everyone left the class a better programmer than before. Since a CS degree is still, rightly or wrongly, considered the sole requirement for many programming jobs, I think it was time well spent.