Fix Peter Norvig citation
This commit is contained in:
parent
182c1edaa3
commit
95ddd72804
2 changed files with 10 additions and 10 deletions
|
@ -3033,6 +3033,15 @@ New York, NY},
|
|||
file = {/home/charlotte/sync/Zotero/storage/SHENAY3T/Nirmalakhandan et al. - 2007 - Teaching Tools to Promote Active Learning Case St.pdf;/home/charlotte/sync/Zotero/storage/GHF6GZKB/(ASCE)1052-3928(2007)1331(31).html}
|
||||
}
|
||||
|
||||
@misc{norvigTeachYourselfProgramming2001,
|
||||
title = {Teach {{Yourself Programming}} in {{Ten Years}}},
|
||||
author = {Norvig, Peter},
|
||||
year = {2001},
|
||||
urldate = {2022-08-16},
|
||||
howpublished = {http://norvig.com/21-days.html},
|
||||
file = {/home/charlotte/sync/Zotero/storage/VTNWVKYG/21-days.html}
|
||||
}
|
||||
|
||||
@article{nustRockerversePackagesApplications2020,
|
||||
title = {The {{Rockerverse}}: {{Packages}} and {{Applications}} for {{Containerisation}} with {{R}}},
|
||||
shorttitle = {The {{Rockerverse}}},
|
||||
|
@ -3227,15 +3236,6 @@ New York, NY},
|
|||
file = {/home/charlotte/sync/Zotero/storage/BSENXYMJ/Pedregosa et al. - 2011 - Scikit-learn Machine Learning in Python.pdf}
|
||||
}
|
||||
|
||||
@misc{peternorvigTeachYourselfProgramming2001,
|
||||
title = {Teach {{Yourself Programming}} in {{Ten Years}}},
|
||||
author = {{Peter Norvig}},
|
||||
year = {2001},
|
||||
urldate = {2022-08-16},
|
||||
howpublished = {http://norvig.com/21-days.html},
|
||||
file = {/home/charlotte/sync/Zotero/storage/VTNWVKYG/21-days.html}
|
||||
}
|
||||
|
||||
@inproceedings{petitJutgeOrgEducational2012,
|
||||
title = {Jutge.Org: An Educational Programming Judge},
|
||||
shorttitle = {Jutge.Org},
|
||||
|
|
2
book.org
2
book.org
|
@ -1150,7 +1150,7 @@ All submitted solutions are stored, but for each assignment only the last submis
|
|||
This allows students to update their solutions after the deadline (i.e.\nbsp{}after model solutions are published) without impacting their grades, as a way to further practice their programming skills.
|
||||
One effect of active learning, triggered by mandatory assignments with weekly deadlines and intermediate tests, is that most learning happens during the term (Figure\nbsp{}[[fig:usefwecoursestructure]]).
|
||||
In contrast to other courses, students do not spend a lot of time practising their coding skills for this course in the days before an exam.
|
||||
We want to explicitly encourage this behaviour, because we strongly believe that one can not learn to code in a few days' time\nbsp{}[cite:@peternorvigTeachYourselfProgramming2001].
|
||||
We want to explicitly encourage this behaviour, because we strongly believe that one can not learn to code in a few days' time\nbsp{}[cite:@norvigTeachYourselfProgramming2001].
|
||||
|
||||
For the assessment of tests and exams, we follow the line of thought that human expert feedback through source code annotations is a valuable complement to feedback coming from automated assessment, and that human interpretation is an absolute necessity when it comes to grading\nbsp{}[cite:@staubitzPracticalProgrammingExercises2015; @jacksonGradingStudentPrograms1997; @ala-mutkaSurveyAutomatedAssessment2005].
|
||||
We shifted from paper-based to digital code reviews and grading when support for manual assessment was released in version 3.7 of Dodona (summer 2020).
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue