Wanted: Advice from CS teachers
-
I think they become anxious when their code isn't working the same as what I have up on the projector and they want to get it fixed RIGHT AWAY so they won't fall behind.
Then when one of them starts calling out they all do it.
I may take some time to explain this.
This never happens when I'm teaching math. Something about coding makes them forget some of their manners, and become less self-sufficient. "It's broke! I'm helpless!"
What is that about?
@futurebird one part of it may be that you get instant-ish feedback. When you're doing a math problem with pen and paper, you can write down a wrong answer and not know it until someone shows the expected answer.
That "run"/"compile" button (or IDE feedback / warnings) is happy to tell you almost immediately if there's something the computer can't figure out. And since the computer does a bunch of big mysterious stuff (and is always right), if there's a problem, it's definitely that YOU are WRONG.
Starting with something about getting unstuck on your own (and grounding it in patterns they already know from math) sounds like a good idea.
-
@unlambda @EricLawton @maco @futurebird @david_chisnall All of this. I remain with a position of "this is a net negative for society”. However the utility to a programmer is pretty hard to deny.
The utility to employers of programmers, yes.
I'm not clear how individual programmers benefit. Obviously not those who are laid off.
Not for those who take pride in their work. -
The utility to employers of programmers, yes.
I'm not clear how individual programmers benefit. Obviously not those who are laid off.
Not for those who take pride in their work.@EricLawton @unlambda @maco @futurebird @david_chisnall i disagree with some strong asterisks. But I do think that making something you can really be proud of in detail is a bit uphill.
But also this enables a lot of time to spend on the planning and documenting side of things, which are absolutely things that programmers have wanted more time to do well, and processes that support. This might be providing them.
-
@futurebird
So that was step one, teach their eyes to pick info from the error text, instead of sliding off it. Next step teach them to see error as a call for their action. I did this by running through 2-3 common errors and the action, repeating 'WHEN I see an X error, THEN I do Y' language.WHEN I see a NameError, THEN I read the error, look up the line, and look for a mistyped name.
WHEN I see a SyntaxError, THEN I double-check my quote marks / parentheses / colons.
2/
Also IndentError, KeyError, and IndexError.
(Optional: 'hunt the Big Five': can they deliberately make code that has this error? and then fix it?)
Finally TypeError, for which more than the previous errors the fix depends on what you were doing. New phrase: 'I THOUGHT I had a number, but I HAVE a string. Can I change what I HAVE, or should I change what I THINK?"
Change what I have: int(my_string)
Change what I think: Ah, x can also be a string. `if type(my_x) is str: ...`
3/ -
@EricLawton @unlambda @maco @futurebird @david_chisnall i disagree with some strong asterisks. But I do think that making something you can really be proud of in detail is a bit uphill.
But also this enables a lot of time to spend on the planning and documenting side of things, which are absolutely things that programmers have wanted more time to do well, and processes that support. This might be providing them.
(Certainly not all programmers, but people proud of the craft and of doing a good job.)
-
@futurebird @maco @EricLawton @david_chisnall Oof. A sales pitch embedded in it sounds miiiiiserable.
As far as pricing ... man it's hard to tell. The training of models is very expensive, and energy-consuming. That has to be amortized somehow. But the actual running takes only a little more than 'home computer' level. (and cruddier models do run on home computer scale things)
@aredridel @futurebird @maco @EricLawton @david_chisnall but the actual running of all these popular LLMs has long ago outgrown the training? With vast majority of e.g. OpenAI expenses being on inference and not on training.
-
So Your Code Won't Run
1. There *is* an error in your code. It's probably just a typo. You can find it by looking for it in a calm, systematic way.
2. The error will make sense. It's not random. The computer does not "just hate you"
3. Read the error message. The error message *tries* to help you, but it's just a computer so YOUR HUMAN INTELLIGENCE may be needed to find the real source of error.
4. Every programmer makes errors. Great programmers can find and fix them.
1/
@futurebird
Wonderful. I would suggest a small change to 4. Even though the rest of your message explains how to become a great programmer, students may get hyper-fixated on #4. They may think "oh I'm just not a great programmer" before even reading ahead, or even after. So may I suggest something like: "Finding and fixing the errors is an essential step towards becoming a great programmer." This frames it as a process from the get-go, rather than a binary. -
@aredridel @futurebird @maco @EricLawton @david_chisnall but the actual running of all these popular LLMs has long ago outgrown the training? With vast majority of e.g. OpenAI expenses being on inference and not on training.
@IngaLovinde @futurebird @maco @EricLawton @david_chisnall Yup. Not mostly for coding, where the demand is pretty direct, but ChatGPT is wildly popular itself _and_ wildly integrated even in the most ridiculous places. So even in the places it's hated, someone's inducing demand.
-
Also IndentError, KeyError, and IndexError.
(Optional: 'hunt the Big Five': can they deliberately make code that has this error? and then fix it?)
Finally TypeError, for which more than the previous errors the fix depends on what you were doing. New phrase: 'I THOUGHT I had a number, but I HAVE a string. Can I change what I HAVE, or should I change what I THINK?"
Change what I have: int(my_string)
Change what I think: Ah, x can also be a string. `if type(my_x) is str: ...`
3/Okay, last bits, sorry for going on so long!
1. My inspiration was Software Carpentry's module on reading errors. https://swcarpentry.github.io/python-novice-inflammation-2.7/07-errors.html
2. I also taught them about 'rubber ducking'. Made it all conspiratorial, let them in on the secret, tell them the pros do this. (We do!) The secret is: draw a little duck, and when you get errors explain your problem to the duck. Duck is simple duck, so explain every detail. Often, because you explain it, you'll realise how to fix it! 4/4 -
That is something I should definitely try sometime.
When the broken code comes from another person, it is more "improving something" and less "getting your work dissected".
@wakame @futurebird and i do need to brag about one of them. one day one of the interns told me of how she started getting answer to problems she couldn't figure out. she created 2 stack overflow accounts, with her main she asked her question. with her alt, she'd confidently give herself a wring answer. and then sit back and wait for the well actuallies. i was so proud
-
So Your Code Won't Run
1. There *is* an error in your code. It's probably just a typo. You can find it by looking for it in a calm, systematic way.
2. The error will make sense. It's not random. The computer does not "just hate you"
3. Read the error message. The error message *tries* to help you, but it's just a computer so YOUR HUMAN INTELLIGENCE may be needed to find the real source of error.
4. Every programmer makes errors. Great programmers can find and fix them.
1/
@futurebird I mean, the computer *does* just hate you, but that's not why your code isn't running. Completely separate issue.
-
@futurebird I know what you mean, and you're perfectly right when it comes to sane programming languages. However, C++ compilers have a habit of spewing out error messages the size of a Tolstoy novel in response to mistakes as trivial as a missing comma. Now I assume you're not teaching the kids C++ as that would be quite irresponsible.
@mansr @futurebird *cries in PHP*
-
Wanted: Advice from CS teachers
When #teaching a group of students new to coding I've noticed that my students who are normally very good about not calling out during class will shout "it's not working!" the moment their code hits an error and fails to run. They want me to fix it right away. This makes for too many interruptions since I'm easy to nerd snipe in this way.
I think I need to let them know that fixing errors that keep the code from running is literally what I'm trying to teach.
@futurebird random : don't do big changes. Do small changes and validate with compiler or tests. That usually solves 90% of problems.
-
Wanted: Advice from CS teachers
When #teaching a group of students new to coding I've noticed that my students who are normally very good about not calling out during class will shout "it's not working!" the moment their code hits an error and fails to run. They want me to fix it right away. This makes for too many interruptions since I'm easy to nerd snipe in this way.
I think I need to let them know that fixing errors that keep the code from running is literally what I'm trying to teach.
@futurebird I'm gonna be brief because I'm a parent, not a teacher, but this experience rhymes with mine.
what I tend to do is respond in a way that addresses the existence of a good question without answering it. even if the response equates to "I'm doing something so I'm not ready to help with that yet", I try to encourage the aspect of wondering. so for example "you've stumbled on a surprise part of the lesson! it's ok, keep following along while i get everyone there."
or something. I'm just a guy.
-
I’ve taught programming like this, but I’m an increasingly huge fan of the debugging-first approach that a few people have been trying more recently. In this model, you don’t teach people to write code first, you teach them to fix code first.
I’ve seen a bunch of variations of this. If you have some kind of IDE (Smalltalk is beautiful for this, but other languages usually have the minimum requirements) then you can start with some working code and have them single-step through it and inspect variables to see if the behaviour reflects their intuition. Then you can give them nearly correct code and have them use that tool to fix the issues.
Only once they’re comfortable with that do you have them start writing code.
Otherwise it’s like teaching them to write an essay without first teaching them how to erase and redraft. If you teach people to get stuck before teaching them how to unstick themselves, it’s not surprising that they stop and give up at that point.
@david_chisnall @futurebird I remember being excited when I learned Ruby was supposed to be a test-first language (you design the tests then code to them)
Unfortunately, the language was Ruby and few if any of its users even tried to adopt such an ideology.
But I agree with you! On that, have any reading materials with tips for modern practices, I'm still clinging to a worn copy of 'Working Effectively With Legacy Code'
-
I think they become anxious when their code isn't working the same as what I have up on the projector and they want to get it fixed RIGHT AWAY so they won't fall behind.
Then when one of them starts calling out they all do it.
I may take some time to explain this.
This never happens when I'm teaching math. Something about coding makes them forget some of their manners, and become less self-sufficient. "It's broke! I'm helpless!"
What is that about?
@futurebird I think it’s because code is supposed to do something. So when it doesn’t they get anxious. I still have this whenever I do a training and for some reason my code doesn’t work. It’s a fear of falling behind and a feeling of inadequacy
-
Wanted: Advice from CS teachers
When #teaching a group of students new to coding I've noticed that my students who are normally very good about not calling out during class will shout "it's not working!" the moment their code hits an error and fails to run. They want me to fix it right away. This makes for too many interruptions since I'm easy to nerd snipe in this way.
I think I need to let them know that fixing errors that keep the code from running is literally what I'm trying to teach.
@futurebird ive been having the exact same problem haha. i think maybe it helps to have moments where, if everything goes right, the program will crash in a particular way, and we can look at what the error is saying and then at what that actually means. perhaps?
-
Things to Try:
* look for typos
* look at what the error message indicates.If these don't work consider reverting your last changes to the last working version of your code. Then try making the changes again, but be more careful.
If you can't revert the changes, start removing bits of the code systematically. Remove the things you think might cause the error and run the code again. Isolate the change or code that causes the problem.
You can be a great programmer.
2/2
@futurebird reminds me of the helpful guides in the Usborne books I learnt programming from.
-
Wanted: Advice from CS teachers
When #teaching a group of students new to coding I've noticed that my students who are normally very good about not calling out during class will shout "it's not working!" the moment their code hits an error and fails to run. They want me to fix it right away. This makes for too many interruptions since I'm easy to nerd snipe in this way.
I think I need to let them know that fixing errors that keep the code from running is literally what I'm trying to teach.
@futurebird I address this issue by giving students a working program and have them purposely make mistakes to see what happens: https://langintro.com/comsc020/lets-think-python.pdf (page 22) You might even want to make a contest for “who can get the most error messages/ weirdest error message with a mistake in one line?”
As for looking at the wrong line for the error, I use the analogy of buttoning your shirt wrong. You find out it’s wrong when you run out of buttons at the bottom of the shirt, but that’s not where the error really started. (https://youtu.be/kJ4FGD2sQzE)
-
Example of the problem:
Me: "OK everyone. Next we'll make this into a function so we can simply call it each time-"
Student 1: "It won't work." (student who wouldn't interrupt like this normally)
Student 2: "Mine's broken too!"
Student 3: "It says error. I have the EXACT same thing as you but it's not working."
This makes me feel overloaded and grouchy. Too many questions at once. What I want them to do is wait until the explanation is done and ask when I'm walking around. #CSEdu
@futurebird I’m not in the education loop. But I saw this with some of the new hires for the last 5-10 years. Rightly or wrongly, I attributed this to the teaching to test mentality. The kids are taught that there are always “right” answers, you cannot figure them out yourself you just have to ask the teacher and they will give it to you. There isn’t time to teach creative problem solving.
