Timeline for Is asking students to debug existing code better than having them write new code?
Current License: CC BY-SA 3.0
25 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 24, 2017 at 23:53 | comment | added | ctrl-alt-delor | I am currently experimenting with getting pupils to modify existing code — I have not been teaching long, but believe that this will have a better outcome that having struggle to start from zero. | |
| Jun 24, 2017 at 12:52 | answer | added | Buffy | timeline score: 1 | |
| Jun 24, 2017 at 10:29 | history | edited | thesecretmaster♦ |
Removed irrelevant tag
|
|
| Jun 24, 2017 at 5:41 | answer | added | cMcNerlin | timeline score: 3 | |
| Jun 23, 2017 at 19:58 | answer | added | luizfzs | timeline score: 2 | |
| Jun 23, 2017 at 19:33 | comment | added | Luke Sawczak | Incidentally, as someone who's done both CS and French teaching-related work, I think there's an analogy with "Should I have students write their own French or edit and translate others'?" The answer is simply yes :) The more methods you can throw at a student for interacting with the material, the better it will stick, and also the more likely they'll discover what they love most. Similarly, in the CS courses I was helping with, there were lectures, guided labs, unguided labs, larger assignments, tiny Q&As , mutual code reviews, puzzles, etc. — every possible tool. I thought it was great. | |
| Jun 23, 2017 at 18:02 | answer | added | EJoshuaS - Stand with Ukraine | timeline score: 2 | |
| Jun 23, 2017 at 17:20 | answer | added | Geoff Snowman | timeline score: 2 | |
| Jun 23, 2017 at 16:22 | answer | added | Uncle Long Hair | timeline score: 3 | |
| Jun 23, 2017 at 14:01 | comment | added | Voo | In my opinion it's not so much about the debugging (they'll do that anyhow on their own applications as well, although certainly it's different) but just the simple act of reading other people's code. In my opinion that's taught way too little if at all in university, but it is oh so very, very, very essential. | |
| Jun 23, 2017 at 3:36 | comment | added | atk | what makes you believe that any practical application can actually be error free? | |
| Jun 22, 2017 at 20:40 | answer | added | Meower68 | timeline score: 8 | |
| Jun 22, 2017 at 20:40 | answer | added | MIKE | timeline score: 2 | |
| Jun 22, 2017 at 19:48 | comment | added | AlG | What age group? In my undergrad work our faculty had all "come from the industry" so our work included large projects that were broke and required fixing before augmenting, creation work, and larger group projects where you had to collaborate, integrate and debug. All I'd say made me a better developer when I graduated. | |
| Jun 22, 2017 at 19:44 | answer | added | Ross Heitkamp | timeline score: 15 | |
| S Jun 22, 2017 at 18:28 | history | suggested | CommunityBot | CC BY-SA 3.0 |
improved grammar
|
| Jun 22, 2017 at 18:23 | review | Suggested edits | |||
| S Jun 22, 2017 at 18:28 | |||||
| Jun 22, 2017 at 14:58 | answer | added | John McManus | timeline score: 4 | |
| Jun 22, 2017 at 14:58 | comment | added | Darren Bartrup-Cook | Maybe write code, pass it to your neighbour and have them debug it. | |
| Jun 22, 2017 at 14:55 | comment | added | Baldrickk | Introduce them to TDD early. It's good for both breaking down tasks to develop algorithms, and for producing quality code in the first place. Not to mention that it's a very good habit to have. | |
| Jun 22, 2017 at 14:16 | comment | added | PTwr | Why not both? Give them group project with full code-review and proper testing. | |
| Jun 22, 2017 at 12:19 | answer | added | Ben I.♦ | timeline score: 15 | |
| Jun 22, 2017 at 12:10 | history | edited | Ben I.♦ | CC BY-SA 3.0 |
Fixed grammar
|
| Jun 22, 2017 at 11:57 | answer | added | Brett Becker | timeline score: 3 | |
| Jun 22, 2017 at 11:46 | history | asked | i-- | CC BY-SA 3.0 |