We've had a course running for a couple of years now that seeks to addresses these issues, as well as the inherently collaborative nature of software engineerin

We've had a course running for a couple of years now that seeks to addresses these issues, as well as the inherently collaborative nature of software engineering. It's a second year course that in its first two iterations had approximately 70 students working on a common code-base: tinkering, extending, integrating their work, etc. This year we have 170 students. And we're on a path towards opening the course to the world. (This also means that rather than have students work on small greenfield exercises, they're working on a project that in terms of numbers-of-programmers is possibly larger than some of them will work on in their first post-degree jobs.) It's a follow-on to a more introductory programming course -- we expect students to come in to our course knowing the basic syntax of the language. papers for those who might be interested: Billingsley, W. & Steel, J. 2013. A comparison of two iterations of a software studio course based on continuous integration. ACM conference on Innovation and technology in computer science education (ITICSE). 213-218 Süß, J.G & Billingsley, W. 2012 Using continuous integration of code and content to teach software engineering with limited resources. International Conference on Software Engineering (ICSE). 1175-1184 (I also posted this as a comment on the article itself, so apologies if you see it in two places.)