(I'l admit to being inspired by all the part work magazine adverts that appear at this time of year [Week by week you will learn how to build a full size Spitfire, part one contains your first .50 calibre machinegun])
Its also shown that me being on European time is a serious barrier to attendees. So here are a couple of other ideas I had that anyone is welcome to take and develop:
Three projects come to mind, build a gun, build a car and build an aircraft. Start at the beginning, go through the scripts on a line by line basis explaining both the reason you need the code and how the code works. Dont provide the code , let your attendees creat e their own, that way they can adapt as they want, and are more likely to learn what the code is doing and why. Small examples demonstrating key functions are good, especially if your students can adapt them them to create the basic code. Be prepared to have to correct some dodgy code.
In a similar line, what about a "How does it work?" course. Take something like the Linden pop gun, or the basic flight script and once again go through it on a line by line basis explaining how each event and function works and why its needed. The advantage with this one is you dont actually have to develop any code yourself.
Give them homework. Absolutely no reason to, but its fun seeing the reaction when you tell them ("He wants us to write our own brain script?"
I havnt planned it yet, but its in my mind to do show and tell event afterwards where everyone can show off their new creation.
I would recommend anyone interested in starting their own multi-part project course to take a look at Catfart's teaching layout.
