FRC Primer for Programmers

[Monochron]

Originally Posted by rich2202

It is an overview, not in depth. It is a one session overview, not a summer long class.

It still sounds like "one session" is going to take quite a while. If your goal is get students interesting in working on the robot programming, you may want to give higher priority to piquing that interest.

Deploying code is at the end because that is the last thing you do.

Are they not going to deploy any code until the very end? I guess it depends what your goals are for this class. If you have students who are already programmers or who are already certain that they like programming, then you don't need to get them hooked first. And the topics you have planned are all definitely necessary if you want to build a strong programming team. But if you are hoping to grow your programming team with this lesson plan, I'm not so sure.

[jweston]

Originally Posted by rich2202

As my summer project, I am going to create a power point presentation to train new programmers. Note: I am not trying to teach them Java or C++.

May I suggest a slightly differnet approach in order to avoid information overload? Start with a simple code exercise that gives an immediate result, such as making a tank drive train move forward. Let the new students create the project, write/copy the code, and deploy it themselves to see it run. Let the students make simple modifications to the code, such time or distance constants.

As you walk through this simple exercise, you can use additional power point slides to discuss some of the basics like init vs periodic and what the various modes mean. You can also use it to intro tools like the debugger. Having students engaged in a concrete example gives much richer context to what you're saying than having it in power point by itself. This is definitely a time to keep it simple.

Once you've covered what you can through that exercise, decide what you want to illustrate next and design another interactive exercise. The important parts are keep it focused and keep it interactive.

The outline you have strikes me as being great for a reference. A reference provides great value in case someone wants to do some more in-depth reading on a particular topic.

It's tempting to try to ground new students thoroughly in How It All Works. But it's so much more important to not make new students drink from the firehose of information. They will learn through guided doing.

Originally Posted by rich2202

Sitting around watching the experienced programmers is no fun if you have no idea what they are doing.

Sitting around watching the experienced programmers is never fun. Listening to lectures is not fun. Writing code and watching it work is fun.

[Ether]

Originally Posted by jweston

Listening to lectures is not fun.

Not true as an unqualified general proposition. Some students enjoy and thrive on lectures.

But you're probably correct that most new programmers will thrive better with hands-on simple exercises to get them started and pique their interest.

[jweston]

Originally Posted by Ether

Not true as an unqualified general proposition. Some students enjoy and thrive on lectures.

Fair enough. I've been known to enjoy a lecture on the likes of ancient Crete or partical physics. No reason someone shouldn't enjoy an engaging lecture on the finer points on, say, control system programming theory.

I think we can agree that competitve coding as a spectator sport is not likely to take off any time soon.