|
1 There was a setup error with PEP and the Evasys system, because of |
|
2 which we were only able to collect 64 responses (out of 400+ eligible |
|
3 students) this year. The submitted responses indicate that students |
|
4 were satisfied with the module. For example more than 64% of the |
|
5 students found the pace of the lectures about right and more than 81% |
|
6 of the students found the module intellectually stimulating. Furthermore |
|
7 75% od the students we satisfied with the quality of the module, with |
|
8 another 7.8% expressing a neutral opinion. Of course we will work |
|
9 hard to maintain, and possibly even improve upon, such a favourable view. |
|
10 |
|
11 Students generally liked learning new programming languages and |
|
12 seeing programming from a different point of view. Also students appreciated |
|
13 very much the setup of coursework and the automatic feedback via Github |
|
14 submissions. We will keep this in the future. We will also keep the two |
|
15 deadlines for the coursework in November and January for the work to |
|
16 be completed. This seems to have worked well with students (as opposed to |
|
17 weekly deadlines we had in previous years). We did not hear about any |
|
18 problems regarding the SGTs and TAs. We will keep the format of weekly |
|
19 SGTs led by an experienced TA. |
|
20 |
|
21 Some difficulties arose from the study material. We will go over the |
|
22 provided material for the next year and implement potential |
|
23 improvements. We inherited this year the software behind the testing |
|
24 framework. We will endeavour to maintain this testing framework, which |
|
25 is a potpourri of scripts written in Perl, Bash, PhP, Python, as well |
|
26 as C++ and Scala, of course. |