- Home
- Search
- Michael Tsiang
- STATS 20
AD
Based on 170 Users
TOP TAGS
There are no relevant tags for this professor yet.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Grade distributions are collected using data from the UCLA Registrar’s Office.
Sorry, no enrollment data is available.
AD
This class is as horrible as everyone else mentioned here. However, this quarter I had a great grader, who points out my errors but gives full credit to my homework. Btw, I completed all parts of the homework and at least wrote complete code, and the graders just grade on completeness instead of correctness. BUT it is just so hard to write complete code. Thus, a nice grader seems great, but it also requires a large amount of time spent on homework.
Finally Mike seemed to give us grades generously, since I was between 25-50 percentile for most exams but still get an A.
If you got another professor for this class, just take it. If not, Mike is not so bad if you have a nice grader.
Not much left to say that hasn't already been said. The reviews for this class are accurate unfortunately (mike is nice but the class sucks a$$). I had Bart as a TA and he was really chill and pretty funny. I would recommend him because he made this class a little better and honestly helped me get through it (not so much content wise but mental stability wise).
Now onto my advice: STUDY !! This may seem obvious to some of you, but it was completely foreign to me to study for a coding class. This class turns through a ton of material, so you need to review everything covered in the notes as well as the HW problems before the midterms and finals (this will help a TON).
I know if you are reading this you probably have to take this class and you probably have to take it with Mike. I'm really sorry and it might be scary reading all these reviews, but I promise you will get through it... just stay confident and good luck (you got this) !!
The professor is a friendly person.
Take this class online (COVID-19)a lot thing may be different from before.
40% for both exam(25%better one 15% lower one) 18% Homework 30% Final exam 12% Final project
Due to the epidemic, the project was cancelled. total grade is over 88.
The time for the exam is tight. I have never completed all the questions.
Exam grade is mostly based on percentiles, top50% A to A-, 50%-75%B+/B range. End 25%B/B-/below range.
Homework can be late for 24h, no points are deducted. Although the homework is difficult, it is scored according to the degree of completion. 75% complete, you can get 100% points . No one will tell you the correct way before due day. It is for "stimulate the learning process". If you don’t have time to think, or if you don’t have any clues. Just answer your plan and ideas will get full marks.
1st exam : min~1st Qu
2nd exam: med~3rd Qu
Final exam: med
Final Grade: A-
(for stats 20)
HW is doable and not extremely time-consuming. If you try each problem honestly, you will receive more scores than you expect. Scoring 100% on HW is definitely possible.
Midterms are HARD, so the grades might be frustrating. The final is long and cumulative but not necessarily as hard since you have more time, so just make sure you have a solid foundation on the earlier chapters and study the later chapters well.
Don't give up learning the later chapters if you messed up the two midterms. I did horribly on the two midterms (below the class medians, close to the avgs), but then I got 90+ in the final by rewatching some of the lectures, taking notes on details taught in the lecture that was easily overlooked, playing with weird edge cases in R, and redoing some short HW problems. I ended up with an A.
The lectures are definitely helpful, but you still have to figure out lots of things in the HW by yourself (I mean searching on the internet is not helpful since you are not allowed to use outside sources). I never went to OHz, but I guess that may also help. On the Campuswire forum, some people asked questions that I never encountered in the HW or lectures, but thinking about some of those questions helped me understand the concepts.
I thought Stats 20 with Mike was great! Learning how to code in R is like learning a new language, but it is because of Mike and my awesome TA Bart that I feel like I have a solid comprehension of R for the upper division stats courses to come. The class breakdown was 7 homeworks (graded on completion), 2 midterms, and a final exam. The homework assignments were difficult, but always referenced material learned in the chapter notes that Mike lectured through. What I appreciated is as someone who is new to programming is that Mike standardized this class so that everyone must use the same base level functions and structure, making this class doable as an introduction. The graders for the homework always left helpful comments on how to improve your code. The midterm exams and final were all very difficult given the time frame, but as long as you understand the notes and the examples Mike emphasizes, you will perform fine. Plus the class is scaled generously. Overall - Mike is a great guy, and you should take him if you can, especially with Bart. They are both very accommodating and caring! My advice is that you should study his notes, work through the examples, and trust your gut instinct for coding on exams! :)
He must have changed the class since 2019, because it's definitely an average class now. He has about 4 hours of lecture/week, and the hw takes about 4 hours. 80% of the hw answers is straight from his notes on ccle, and the rest you can just ask for hints on campuswire forum. The hw is also graded on completion. And honestly, Mike is a super understanding prof, if you're stressed about grades, you can work with him to figure something out. As for the midterms, so the averages were like 60's, but the grading scale is generous:
75+ percentile = A+
50+ percentile = A-/A
25+ percentile = B/A-
0+ percentile = <B
Yes, the class is tough. But, it is extremely valuable to take the course with Mike, if you plan to go on to major in Stats and take the 101 and 102 series. He is very welcoming, super nice, and willing to really help his students in order to make sure that they truly comprehend the material... if they put in the necessary work. Go to office hours, start the problem sets (they're long!) way ahead of time and you should be more than fine for the course.
If there is a class which will stress you out and mess up your mental health it is this one.
Save your self and if you have any intention of having a social life to even a little little amount, don't take it(PLZZ )
This class is as horrible as everyone else mentioned here. However, this quarter I had a great grader, who points out my errors but gives full credit to my homework. Btw, I completed all parts of the homework and at least wrote complete code, and the graders just grade on completeness instead of correctness. BUT it is just so hard to write complete code. Thus, a nice grader seems great, but it also requires a large amount of time spent on homework.
Finally Mike seemed to give us grades generously, since I was between 25-50 percentile for most exams but still get an A.
If you got another professor for this class, just take it. If not, Mike is not so bad if you have a nice grader.
Not much left to say that hasn't already been said. The reviews for this class are accurate unfortunately (mike is nice but the class sucks a$$). I had Bart as a TA and he was really chill and pretty funny. I would recommend him because he made this class a little better and honestly helped me get through it (not so much content wise but mental stability wise).
Now onto my advice: STUDY !! This may seem obvious to some of you, but it was completely foreign to me to study for a coding class. This class turns through a ton of material, so you need to review everything covered in the notes as well as the HW problems before the midterms and finals (this will help a TON).
I know if you are reading this you probably have to take this class and you probably have to take it with Mike. I'm really sorry and it might be scary reading all these reviews, but I promise you will get through it... just stay confident and good luck (you got this) !!
The professor is a friendly person.
Take this class online (COVID-19)a lot thing may be different from before.
40% for both exam(25%better one 15% lower one) 18% Homework 30% Final exam 12% Final project
Due to the epidemic, the project was cancelled. total grade is over 88.
The time for the exam is tight. I have never completed all the questions.
Exam grade is mostly based on percentiles, top50% A to A-, 50%-75%B+/B range. End 25%B/B-/below range.
Homework can be late for 24h, no points are deducted. Although the homework is difficult, it is scored according to the degree of completion. 75% complete, you can get 100% points . No one will tell you the correct way before due day. It is for "stimulate the learning process". If you don’t have time to think, or if you don’t have any clues. Just answer your plan and ideas will get full marks.
1st exam : min~1st Qu
2nd exam: med~3rd Qu
Final exam: med
Final Grade: A-
(for stats 20)
HW is doable and not extremely time-consuming. If you try each problem honestly, you will receive more scores than you expect. Scoring 100% on HW is definitely possible.
Midterms are HARD, so the grades might be frustrating. The final is long and cumulative but not necessarily as hard since you have more time, so just make sure you have a solid foundation on the earlier chapters and study the later chapters well.
Don't give up learning the later chapters if you messed up the two midterms. I did horribly on the two midterms (below the class medians, close to the avgs), but then I got 90+ in the final by rewatching some of the lectures, taking notes on details taught in the lecture that was easily overlooked, playing with weird edge cases in R, and redoing some short HW problems. I ended up with an A.
The lectures are definitely helpful, but you still have to figure out lots of things in the HW by yourself (I mean searching on the internet is not helpful since you are not allowed to use outside sources). I never went to OHz, but I guess that may also help. On the Campuswire forum, some people asked questions that I never encountered in the HW or lectures, but thinking about some of those questions helped me understand the concepts.
I thought Stats 20 with Mike was great! Learning how to code in R is like learning a new language, but it is because of Mike and my awesome TA Bart that I feel like I have a solid comprehension of R for the upper division stats courses to come. The class breakdown was 7 homeworks (graded on completion), 2 midterms, and a final exam. The homework assignments were difficult, but always referenced material learned in the chapter notes that Mike lectured through. What I appreciated is as someone who is new to programming is that Mike standardized this class so that everyone must use the same base level functions and structure, making this class doable as an introduction. The graders for the homework always left helpful comments on how to improve your code. The midterm exams and final were all very difficult given the time frame, but as long as you understand the notes and the examples Mike emphasizes, you will perform fine. Plus the class is scaled generously. Overall - Mike is a great guy, and you should take him if you can, especially with Bart. They are both very accommodating and caring! My advice is that you should study his notes, work through the examples, and trust your gut instinct for coding on exams! :)
He must have changed the class since 2019, because it's definitely an average class now. He has about 4 hours of lecture/week, and the hw takes about 4 hours. 80% of the hw answers is straight from his notes on ccle, and the rest you can just ask for hints on campuswire forum. The hw is also graded on completion. And honestly, Mike is a super understanding prof, if you're stressed about grades, you can work with him to figure something out. As for the midterms, so the averages were like 60's, but the grading scale is generous:
75+ percentile = A+
50+ percentile = A-/A
25+ percentile = B/A-
0+ percentile = <B
Yes, the class is tough. But, it is extremely valuable to take the course with Mike, if you plan to go on to major in Stats and take the 101 and 102 series. He is very welcoming, super nice, and willing to really help his students in order to make sure that they truly comprehend the material... if they put in the necessary work. Go to office hours, start the problem sets (they're long!) way ahead of time and you should be more than fine for the course.
If there is a class which will stress you out and mess up your mental health it is this one.
Save your self and if you have any intention of having a social life to even a little little amount, don't take it(PLZZ )
Based on 170 Users
TOP TAGS
There are no relevant tags for this professor yet.