-
-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some exercises are very long #113
Comments
Thank you for the feedback! The local storage vec exercise is indeed too big. Multiple others have raised this concern in the past. I think it'd be best to replace it with some other exercise about implementing traits for a generic struct, and to then mark the local storage vec exercise as bonus. Do you have ideas for an alternative exercise here? About the quizzer: yes that one is big too. However, in this case the intention is to set up a proper project yourself, which is intrinsicly large if the goal is to have the students mess around a bit with structuring a somewhat large crate. I think this one can be left in, but it'd be nice to provide some sort of heads up about the size |
Sounds good. How about a |
Hmm. Would only really make sense for a |
This may be deliberate, but I have noticed that there is a wide variation in the amount of time some of the exercises take. If it is deliberate, maybe it's worth providing some notes so that lecturers can judge when and how to set the work.
Most of the questions seemed to take me 10-30 minutes to complete, but local storage vec took me about 4 hours (see videos part 1 and part 2) and quizzer took me 4h 40 minutes (see video). Admittedly, I am putting in extra time to write robust tests, but even without that these would have taken me a long time.
The text was updated successfully, but these errors were encountered: