Timeline for First project in my second year data structures intro
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 11, 2018 at 15:46 | history | edited | Buffy | CC BY-SA 4.0 | spelling |
| Oct 11, 2018 at 15:15 | comment | added | cryptic_star | One other potential issue I would add to this answer, somewhat related to the five week issue, is that they just can't fathom the steps necessary to break this problem down. I see this all the time in my CS1 and CS2 courses, even for less complex problems. I would either draw out a suggested timeline (e.g., "complete X method by Friday, Y method by Monday"), or have a check in at some point in time. Depending on the number of TAs you have, you could set up gitlab or something similar for students to check in their code periodically, and the TAs to assess whether they are making progress. | |
| Oct 9, 2018 at 21:21 | comment | added | Scott Rowe | I saw situations like this in a college course I took in 1984: many students befuddled and unable to develop a working algorithm. We had no automated testing system, and limited access to computer terminals (mainframe environment). As you say, the info about why submissions failed is vital to figuring out the OPs problem. Coaching the students in incremental build and test would be valuable. | |
| Oct 9, 2018 at 20:50 | comment | added | Ilkka Kokkarinen | That postmortem is a great idea. I will definitely instruct my TA's to do that in the next week's lab. | |
| Oct 9, 2018 at 17:55 | history | answered | Buffy | CC BY-SA 4.0 |