Professor
Petros Faloutsos
1 of 1
Most Helpful Review
The other post make it clear that this professor is crazily ridiculous and no good at teaching. I am going to tell something you didn't know already. Lecture: Slide-based (obviously, you want to see pretty picture rather some badly hand-draw). You should go to lecture if you want to remember the slide. Also maybe it is just me, the slide change; so he post the initial slide on courseweb. Then I redownload it, the slides change (more slide added). I cannot just print out the slide one time because it sometimes edit. This class is heavily math. Project: 1 = easy You should try your best doing project 2, because there will a popularity "contest", the prize is a future letter of recommendation by the professor if you want to go to graphic field or graduate school. 3 = "hardest". I don't know why, because this is the easiest for me ever. As said on other post, there are always 30+ experienced programmer, don't expect any curved. Also, you need to know the following class policy: *Important* To pass the course you must complete successfully 40% of the assignments at minimum. In other words, your assignments must contribute at minimum 18% towards your final grade. Most people will fail on project 3 if they are not experienced programmer. Textbook: Edward Angel, Interactive Computer Graphics, Fifth Edition, Addison Wesley, 2009. is the worst book ever. It might get you to start OpenGL if you don't know how to use openGL, but I think the professor heavily base his lecture on this optional book Computer Graphics: Principles and Practice, 2nd ed. in C, Addison Wesley, 1990. It is better to buy this optional text. TA: Shawn is the best TA you get for this class. He will help you on project 3 as much as he can, but he will not tells you what to program. Exam: midterm = practice midterm up to 80% final = questions people miss on midterm + practice final + few other slide questions In this quarter, the professor tells Shawn not to give out any answer for the final practice. Shawn tells the class that, I don't think he knows, in exact word, "in the past, the final does not look like practice final as the midterm to the practice midterm". If you look at this scheme, if you don't do well on the midterm, you cannot get A, because for people who did well on the midterm, the "questions most people miss on midterm" on the final will look like extra credit; unless by some chance, lightning strikes and they have a amnesia. So the battle is either won or lost when you do the midterm; because there are hardly any curve.
The other post make it clear that this professor is crazily ridiculous and no good at teaching. I am going to tell something you didn't know already. Lecture: Slide-based (obviously, you want to see pretty picture rather some badly hand-draw). You should go to lecture if you want to remember the slide. Also maybe it is just me, the slide change; so he post the initial slide on courseweb. Then I redownload it, the slides change (more slide added). I cannot just print out the slide one time because it sometimes edit. This class is heavily math. Project: 1 = easy You should try your best doing project 2, because there will a popularity "contest", the prize is a future letter of recommendation by the professor if you want to go to graphic field or graduate school. 3 = "hardest". I don't know why, because this is the easiest for me ever. As said on other post, there are always 30+ experienced programmer, don't expect any curved. Also, you need to know the following class policy: *Important* To pass the course you must complete successfully 40% of the assignments at minimum. In other words, your assignments must contribute at minimum 18% towards your final grade. Most people will fail on project 3 if they are not experienced programmer. Textbook: Edward Angel, Interactive Computer Graphics, Fifth Edition, Addison Wesley, 2009. is the worst book ever. It might get you to start OpenGL if you don't know how to use openGL, but I think the professor heavily base his lecture on this optional book Computer Graphics: Principles and Practice, 2nd ed. in C, Addison Wesley, 1990. It is better to buy this optional text. TA: Shawn is the best TA you get for this class. He will help you on project 3 as much as he can, but he will not tells you what to program. Exam: midterm = practice midterm up to 80% final = questions people miss on midterm + practice final + few other slide questions In this quarter, the professor tells Shawn not to give out any answer for the final practice. Shawn tells the class that, I don't think he knows, in exact word, "in the past, the final does not look like practice final as the midterm to the practice midterm". If you look at this scheme, if you don't do well on the midterm, you cannot get A, because for people who did well on the midterm, the "questions most people miss on midterm" on the final will look like extra credit; unless by some chance, lightning strikes and they have a amnesia. So the battle is either won or lost when you do the midterm; because there are hardly any curve.
Most Helpful Review
The problem with this class is it is better suited for math majors than computer scientists. There is definetely more math involved than programming, and that's the stuff that's not on the course description. I mean we are computer scientists, not mathematicians. The amount of math we have to learn is staggering. Other than that, the first two projects were fun, the third a killer. It's only because the prof and ta don't help you enough, no matter how many times you badger them. It's tough stuff, but they don't set up enough groundwork. This class is more theory than praticality, and I would loved for the prof to show more practical stuff in lectures, which were entirely theory His exams are really hard...and the curve won't help cause there are always a few 30+ experienced programmers who are undergrads around... and btw, the lectures are really boring
The problem with this class is it is better suited for math majors than computer scientists. There is definetely more math involved than programming, and that's the stuff that's not on the course description. I mean we are computer scientists, not mathematicians. The amount of math we have to learn is staggering. Other than that, the first two projects were fun, the third a killer. It's only because the prof and ta don't help you enough, no matter how many times you badger them. It's tough stuff, but they don't set up enough groundwork. This class is more theory than praticality, and I would loved for the prof to show more practical stuff in lectures, which were entirely theory His exams are really hard...and the curve won't help cause there are always a few 30+ experienced programmers who are undergrads around... and btw, the lectures are really boring
AD
1 of 1
