I think a good way to deal with this would be assignments that also (partly) prepare you for the written exam. So if you sit down and do it yourself and actually understand the assignment you already did some learning for the exam.

My networking degree was built on a similar principle. A large part of the degree was configuring Cisco switches and routers, which is done through a command line interface, and you can streamline this by copy/pasting a series of commands. The first test was simply setting the hostname, a password and configuring ssh access. This was a full hour+ test, meanwhile by the end of the semester that was the first five minutes of an hour long test to configure more advanced functionality on these devices

The entire degree program was setup so that you take the configs you wrote in the first week and keep building onto them and keep copy/pasting bits and pieces of the configs all the way through graduation and into the workforce.

I could absolutely see a programming degree program taking a similar approach, where you write code snippets in the first class of your freshman year that evolve and you’re ultimately still using by the time you graduate. It forces you to know your code, gives you good code to build off of professionally and makes it really difficult to coast by with nasty hacks and/or AI doing it all for you. It also sets the perfect trap for those trying to have AI do everything for them, where they won’t know what it’s doing or why it’s breaking as the underlying snippets are constantly being changed. Especially if it’s structured with a lot of easy “plumb your existing snippets together” assignments where it’s dead simple for those actually doing the coursework but really hard for those relying on AI entirely. They’ll be forced to learn or drop out which is really important for a college experience!