Changes between Version 2 and Version 3 of pps/HowTo
- Timestamp:
- Feb 2, 2007, 9:57:10 AM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
pps/HowTo
v2 v3 1 = PPS HowTo =1 = PPS !HowTo = 2 2 3 3 You want to know what it takes to make a PPS for a whole semester? 4 4 5 Well you have to be able to answer to many questions from the PPS students. 5 Well you have to be able to answer to many questions from the PPS students. You should either know the modeling program Blender by heart or you have to know a lot of details about the code, the framework, of Orxonox. 6 6 7 7 == Preperation == … … 13 13 * You will NEVER have enought time. no way. 14 14 * Students which loose their handouts won't get any points. 15 * Make sure, that the students know where to get information, so they don't always have to ask you. 16 * 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. 17 * Everybody has to commit a piece of code or a first model in the early weeks to learn the subversion system svn. 15 18 16 19 == Coding/Modeling Phase == 17 20 * Force the students to commit more and more often! 18 21 * Students which don't know svn after 2 months won't get any points. 19 * Send more mails to tell them what's going on, whats next and that they are alreay behind the schedule. 22 * Send more mails to tell them what's going on, whats next and that they are alreay behind the schedule. (Be sure they read them) 20 23 * Students are never finished... invent more tasks ;) 21 24 … … 24 27 * Write an Ad for the Blitz 25 28 * Involve the students with general project tasks (printing the poster, making ads, organising a room...) 29 * Do never prepare something for the students during the lessons. Just work before and after the lessons. 30 * 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 not you have to do all the work. 31 * 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 (the adress of the ETL building is or how to get there). There are several places in Zurich to order a pizza. Some are good, some are really bad. (We recommand Domino's Pizza: One Party Pizza for two hungry PPS-Students) 32 * 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. 26 33 27 34 == Presentation == 28 * 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 not you have to do all the work. 29 * 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 (the adress of the ETL building is or how to get there). There are several places in Zurich to order a pizza. Some are good, some are really bad.30 * 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.35 36 * Make Power Point Slides if you want to show anything theoretically. The design should always be the same. Different designs during a presentation sucks. 37 * You should probably have a presentation branche 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? 31 38 * 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. ;) 32 39