PPS HowTo

You want to know what it takes to make a PPS for a whole semester?

Well, you will have to be able to answer many questions by the PPS students. You should either know the Blender by heart or know a lot of details about the code, the framework of Orxonox.

Preparation

• Define a general style for the content, otherwise the results will differ too much.
• Offer certain projects with very clear tasks and some with a lot of freedom.

Tutorial Phase

• Don't make long presentations… they won't listen anyway.
• You will NEVER have enough time. No way.
• Students which lose their handouts won't get any points.
• Make sure, that the students know where to get information, so they don't always have to ask you.
• Always tell them, that when they get stuck, they should ask you and not just try lots of ways to find a way out. Sometimes you solve their problems with three clicks and they have been working on it for three hours.
• Everybody has to commit a piece of code or a first model in the early weeks to learn about the revision control system SVN.

Coding/Modeling Phase

• Force the students to commit more and more often!
• Students which don't know SVN after 2 months won't get any points.
• Send more mails to tell them what's going on, whats next and that they are already behind the schedule. (Be sure they read them)
• Students are never finished… invent more tasks

End Phase

• Most important: Specify location of presentation EARLY! Write to Reto Kreuzer to ask for a room. Write him a mail about 3 weeks before the presentation.
• Make the poster early. Start the design 3 weeks before the presentation. Print it at the Reprozentrale about 10 days before the presentation. Print approximately 15 posters à A3-size. Just write an email with the link to the poster on our server.
• Alternatively you can print at ETZSPEZ via VPP2: Find more information ​here. Also: I figured out, that PDF does not seem to work, so send the job with PS. Also you will have to cut away white edges if you don't want them. Pricing can be found on the aforementioned website.
• Write an ad for the Blitz. Remember that the last Blitz is published two weeks before semester end (two weeks before the presentation). The deadline for articles will be one week before (so three weeks before presentation). So be quick enough.
• Involve the students with general project tasks (printing the poster, making ads, organizing a room…)
• Do never prepare something for the students during the lessons. Just work before and after the lessons.
• Be sure to reserve some evening and nights to work on Orxonox. You should also drag as many students to those evenings so they work more and you don't have to do all the work.
• On these evenings you should buy pizzas for everyone. Be sure to order them early because the pizza guy is normally quite slow and they don't know where Physikstrasse 3 is (the address of the ETL building) or how to get there. The zip code is 8092! There are several places in Zürich to order a pizza.
  We recommend Domino's Pizza. Buy ½ - 2/3 Dominator Pizzas for each Student (and yourself, of course). Call them (0844 12 12 12) and choose 2, 1, 1 to get connected to the new branch at Universitätsstrasse 11! Since it's so close, you can collect your 'zza at the Universitätsstrasse to get reduction!
• Also do not buy too much beer. You and the students need to be fit to code. We rather suggest a coke as perfect beverage to the pizza.

Presentation

• Make Power Point Slides if you want to show anything theoretically. The design should always be the same. Different designs during a presentation sucks.
• You should probably have a presentation branch right two or one week(s) before the presentation, because then the hacks are implemented and we do not want them in our trunk, do we?
• The presentation itself should be a great show. Of course everything is going to be hacked, but relax as long as it looks good at the presentation.