We had the same issue with the first couple semesters - there were a bunch of us that could breeze through the assignments in a couple hours, which left us most

We had the same issue with the first couple semesters - there were a bunch of us that could breeze through the assignments in a couple hours, which left us most of two weeks till the next one. To combat this we assigned ourselves numerous programming challenges - mostly code for code's sake, but effectively sponging techniques off each other. We effectively competed with each other to see who could do what better. We also went overboard with the assignments a bit - we'd take the basic assignment and "add features" to out-do each other. Often we'd have to hand in a "normal" solution though for marking - the marker didn't appreciate a 20 page printout for a problem that should be half a page of code. And of course there was also some time taken to help others - to effectively give them "extra assignments" to get their code up to scratch. We had access to equipment which we certainly couldn't afford ourselves (although it's laughingly primitive by today's standards) so there was never any shortage of creative ideas. To make things a little more interesting we also signed up for other classes in the science faculty outside of "only" computer science. I did classes in Oceanography and Astronomy, Physics, Applied Maths and so on. The courses were a lot of fun, but the exams were a pain.