80 assignments? What are these assignments? Are you teaching them how to use recursion before looping in Java? I get that Java has some ceremony, but not 70 assignments worth.
The first day I learned to program (with BASIC) I learned looping. I didn't know the details of it (like there was an index variable I could access), but it was as easy as anything else.
Seriously, what are they learning before looping?
See for yourself: http://cs.leanderisd.org/current/cs1/assignments.html
Anyway, the "Swing" assignments are there in the sequence for four reasons:
1) To break up the monotony a little bit. 2) To give them more practice copying details accurately. 3) To make them say, "That was kind of cool." 4) To explain why we're not doing "real" programs (a.k.a. GUI) yet. "It takes that much code just to display a blank window on the screen? Guess I can live with the command prompt a while longer."
I've done a lot of pondering about how to teach programming because I tried to learn several times myself, both on my own and in classes.
I bounced off each time, until finally sticking. I always wonder what made it different that last time, and if it applies to others.
===
Have you considered starting with something with less conceptual overhead than java-in-a-shell? There's so much you need to understand before you can even get to writing code that way. You need to learn how to start and navigate a shell on your computer (different on each type, and depends on your system configuration). You need to learn about paths, and java versions, and sdks, and what 'compiling' even means, and the concept of source code vs a binary.
This doesn't seem like much to people in the field, but I remember it being really intimidating.
In contrast, I really love codecademy.org:
You're writing code within seconds. You can access it on any computer and it always works the same way. Which is to say, it works like any other web site. You start seeing things happen right away, and you don't need to understand all the infrastructure initially.
===
I feel like getting people to that first high where they see their code generate output is really important. If you can get them quickly to feeling a little bit of that power that comes from software, that starts the fire, and they'll have more motivation to figure out terminals and paths and verisons and OSes and everything else.
We install the JDK, do a basic DOS primer, type in our first program (in Notepad), and compile and run it on the command line in a single 90-minute period, like the 3rd day of class.
Getting to the "bang" as quickly as possible is HUGELY important.
I do wonder if your most able students might appreciate more opportunity to "play" and be creative, but in all honesty, they just need to stick with it into the Project Euler stuff at the end.
Is this a whole-year course?
Yes, this is a whole year (36 weeks).
The material you're seeing is only the intro material, though. I teach three other courses, including video game development. The faster students are encouraged to skip assignments if they're coding something they already understand, and they get bonus points if they do something creative with an existing assignment.
I've tried to optimize for the normal case: the weak-to-average student. The great ones however, don't need much help from me to learn a ton very quickly.
I'm a bit disappointed to be honest.
I am very glad I already have been coding for years because our teacher and the planned curriculum seems to confuse people even more.
I think I will refer some people to your assignments, if that's okay? Hopefully someone can learn more from this :-)
I've always thought programming classes should start with reading and understanding a program that has some loops, assignments, etc. Maybe a program that draws some shapes or parses/prints some strings. Then have students modify it some. Then afterward, start writing your own stuff from scratch.
I think you remember things much easier if you write them out (and have to make them compile/execute) yourself. If I read some code in a language I haven't encountered before, I find I don't absorb any of the little details of syntax.
Moreover, I think it makes sense to expose learners to the fun of programming early. And to me that means seeing something that you wrote running.
Perhaps you don't write well until you've read a lot - but nobody expects you to write well as a novice.
I have 75 kids in three sections, and I'd have 100 kids in four sections if they'd open up a fourth section. And all of my students except maybe the bottom 5-10% are moving confidently through the material at their own pace.
I'll bet your school either has 1) a lot fewer students 2) a much more hand-picked set of kids, or 3) is leaving a much higher percentage of kids behind, who are either lost or cheating.
My school is a small (~130 per grade), but renowned international school in Shanghai, China. Your first two guesses are very much spot-on, but I'd have to disagree with the third. Those of us that are ahead help out with the one's who are struggling and in the end, I'd like to think that it all works out well.
With that in mind, however, your numbers are indeed more impressive. Because our class size is so small, we're constantly involved in face-to-face interaction with our instructor and with our peers. I doubt our pace would translate into the same success in your school. Is your course designed for the AP exam?
On the other hand, you learn about laziness, higher-order functions, deterministic and logic programming and how to implement the aforementioned, on top of a bunch of stuff you would learn in a Java class like recursion, OOP and networking. All this in the first four chapters; the fifth one introduces a low-level register based language but my class never got to it :( It is pretty cool.
Ultimately, SICP just has drastically different (and I think better) priorities and topics than any course taught in Java or Python. I also suspect that a good SICP course moves even faster than the material here, simply because of the sheer density of big ideas in the book and the simplicity of Scheme.
I know that when I teach myself anything it's best to focus on one new concept at a time. Scheme's light weight allows all but the CS concepts to fall away from the new coder's consideration.
And why not code in a low-friction way even when not being taught? I wasn't intending to defend FP, but I think it's silly to think of assignment as a fundamental part of CS or the art of coding. It's just one tool.
I was initially far more interested in how I could change the colours of things on screen and get the speaker to make funny noises. Most of what I wrote were text based adventure games so I didn't really need to loop very often.
When I did need to loop I just implemented this using a conditional IF with a GOTO that jumped back to the start of the "block" (I kept paper notes as to which line numbers each subroutine started on) if required or continued to the next line of code.
Later when I started using MS Visual Basic and figured out how to use GOSUB I would do loops essentially with recursion that would call the same subroutine again if required.
It wasn't until I decided to learn C and php that I learnt about real loop structures. At this point I assumed that everything I had done before was stupid and wrong, it was not until I took formal CS classes where I was introduced to recursion and assemly language (JMP and JE) that I realised that pherhaps I hadn't been quite so naieve before.
in logo this is how you draw a square forward 100 Right 90 Forward 100 Right 90 Forward 100 Right 90 Forward 100 Right 90
Then in the second lesson you introduce loops repeat 4 Forward 100 Right 90 End
then you ask kids to draw hexagons octagons etc. and they will never forget what a for loop does.
Edit changed repeat 8 to repeat 4. Thank you.
I don't think it's optimal to make someone type
class Cross extends TurtleGraphicsWindow { public void myTurtleCmds() ...
at the start of every program when they don't yet have the background to understand what a single one of those words are for. It instills a habit of doing crazy shit mindlessly to try to satisfy the mysterious computer.Of course, the College Board, in its infinite wisdom, has decreed that the AP Computer Science tests be given in Java. I suppose we should be grateful that they no longer do it in C++.
This isn't quite right. The teaching language was ABC, a different project that Guido worked on. Python was his own language, created for the Amoeba project (an OS research project), inspired and influenced by, but not the same as, ABC, which was not object oriented. Guido says that the purpose of python for the Amoeba project was to: "bridge the gap between C and the shell"
http://en.wikipedia.org/wiki/ABC_%28programming_language%29
http://python-history.blogspot.com/2009/01/personal-history-...
However, if you have additional information, I'd love to hear about it. I've heard the "Python was originally a teaching language" several times, but as far as I can tell, that's not actually true.
I don't think there was ever any of the boilerplate required to make a Java program actually run. When I took the exam, I'd never compiled a single line of Java in my life (yep, there are far better ways to get things done).
(No sooner than that though, or they'd have to have announced it already; major changes in public education need a LOT of lead time.)
However, I'll disagree that Python would be that much easier than Java for a beginner's course. It's lower-friction, to be sure, but the VAST majority of student difficulties are with precise logical thinking, not with the syntax.
Decomposing a problem into discrete, correctly-ordered steps is the core difficulty. This is unrelated to syntax.
I’ve heard of a CS curriculum that starts by teaching Scheme and ends with a segment on “OK, now you know how to program in Scheme, here is how to do it in Java”. I don’t know if that can fit in one high-school class, though.
You really, really have no idea how difficult precise logical thinking is for an average person.
have you looked at: etoys scratch starlogo alice or scheme ?
At some point soon, I'm planning on moving to something where they can distribute what they're doing, either as JavaScript, or pygame, or something. I'm hoping to be able to literally translate a scratch program to the n+1 environment so that they can see the equivalence of the looping constructs and the event handlers and everything else.
I can't imagine anything that would have pleased me more than being able to show off my own web site when I was that age. Of course, making silly web sites for myself is how I got into programming in the first place, so I'm probably biased ;)
* Runs everywhere. It's the BASIC of this age * It's not that bad. * They can do stuff their friends can see
I'd rather do python, since it's that much cleaner, less curly braces and semicolons and better loops. But, the results aren't as public, and it's a harder environment to set up. And given that I have to work with the school's IT, I think I'm going to be lucky that we can load chrome on the system.
So, clarity for teaching, or ubiquity. Still deciding.
I will say that Stacy Armstrong's "A+ Computer Science" curriculum is quite good and well worth the money.
I've taught Pascal and C++ before, and dabbled in Scheme, too. In my opinion, Scheme is lower-friction than Java, but precise logical thinking is hard in any language, and precise logical recursive thinking is even harder for the average student, which negates any syntax-related benefits.
My kids are very successful in Java, and so I'll stick with what's working until the College Board changes the language of the AP exam on me.
There is now a teaching certificate in just "Computer Science", although it wasn't offered in Texas for a few years while they were switching from one to the other.
Other states vary widely, I'm sure.
It seems that you would at least mention loops early on, to tell them that repetition is something a computer is very good at.
What if the Kahn Academy is teaching the concept in a more clear, concise way than you are? Maybe Java isn't the best language to teach these concepts? Maybe your lessons could be more effective? I don't know what your particular situation is, but I encourage you to play around with your lessons to see if you can teach it as fast as the Kahn Academy. Then again, they could have it totally wrong.
I've taught literally one thousand teenagers to program, face to face. I'd be shocked if Salman Khan had taught even a couple dozen students face to face.
Edit: I accidentally submitted this too early, and then replied instead of editing. See my reply for the rest of this thought.
Then, have all 200 kids attempt to code FizzBuzz on their own, with no assistance. I think probably 60-70% of my students could get it working. I suspect less than 20% of Khan's would have understood/retained enough to get it done.
You are in the 20%, so it's hard for you to see the difference. Salman Khan is in the 1%, and he hasn't been in the trenches long enough to see the difference.
That's what I'm saying.
I really hate taking shots at Khan Academy, because I love what they do and his other videos have really helped a lot of my students in chemistry, economics, etc.
However, he's moving through the material MUCH more quickly than I've ever been able to do as a teacher. And I get nearly 5 hours a week of face time with my students.
For example, his third lecture is on for loops. My students, on the other hand, complete literally 80 assignments before beginning for loops. And they still have some trouble.
Admittedly I'm using Java, and Python is simpler, but I think he's VASTLY underestimating how slowly you need to move through seemly obvious concepts for the average total beginner.