The big problem in schools is that (in my experience, at least) we don't actually have a body of legacy code to provide, and making students use colleagues' sources (something I tried) tends not to give desired results due to... let's call it "emergent quality
of implementation" (it's far from professional code that's evolved over time).
I guess we could make a list of relevant open source projects (with reasons why we think they are relevant) or ask partners from the industry to provide some interesting sources for students to play with... We'd need something stable, however, to avoid students
accessing the work of previous years' students.
De : SG20 <firstname.lastname@example.org> de la part de JC van Winkel via SG20 <email@example.com>
Envoyé : mardi 9 juin 2020 11:47
À : SG20 <firstname.lastname@example.org>
Cc : JC van Winkel <email@example.com>
Objet : Re: [SG20] Wonderful story from Brian Kernighan about an assignment he gave to students.
Glad you liked it.
In general, I like the idea of giving assignments where students need to
change software. That is what happens the most in industry.