General info:
The professor's lectures were pre-recorded and he mostly just read the content in the lecture notes. He has office hours during his normal lecture time.
We had 7 homework assignments (technically 8, but the last one was optional and mostly for final prep) throughout the quarter. Each homework is graded on satisfactory completion (so even if your answer is wrong, if the grader thinks you made a good enough effort, you'll still get full points).
We had a class Campuswire where the professor and TAs were fairly active on. You get extra credit for contributing to Campuswire discussions.
Our final project was cancelled, which was nice.
Tests are very difficult and almost everyone runs out of time. There is usually one question per test that is quite niche in the sense that you probably have never seen what is described in the problem unless you spend a lot of time experimenting around with R. If you want to do well on tests, learn how to debug code quickly, since that will take up a lot of time on tests if you aren't careful.
The raw scores for the midterms were pretty low, but the professor does scale them to increase your score a little.
Some stats for midterms (from the scaled scores, not the raw scores):
Midterm 1: median = 61, mean = 62
Midterm 2: median = 65, mean = 64
I had TA Jake and I interacted with him once in week 1 and then never saw him again. I think he stopped holding discussions after the first week, and I didn't see him post any discussion recordings on CCLE either. Maybe he did post recordings and I just didn't find them, I don't know. I did watch a couple discussion recordings from the other TAs though, they seemed pretty good and they gave some nice debugging examples.
This class is said to be an introductory programming class, but I would not recommend taking this class without any coding experience. There is so much material covered in so little time. If you are new to programming, be prepared to spend 10+ hours (outside of watching lecture videos) on this class per week if you want to get a good grade.
If you are new to coding, have a genuine interest in coding, and want to foster that genuine interest, do NOT take this class as your first programming class. Go take CS 31 instead... trust me.

My experience:
I came in with about 2 years of programming experience (took AP CS in high school, took CS 31, CS 32 at UCLA) and the tests in this class were still a time crunch. Homework assignments took me anywhere between 3 to 8 hours a week, depending on the assignment and how much effort I wanted to put in.
Towards the end of the quarter, I stopped watching lectures and just read the lecture notes, which I found more useful and time efficient.
If you are new to programming or would like to understand debugging more, I would recommend going to discussion. Otherwise, it's not really worth the time.

1.[Difficulty]: ★★★★(If you want an "easy-A GE class", this is IT! The midterms are a little bit tricky with an average score around 86, but the final is a relief. For the final, make sure you understand each material since some concepts are similar to each other and may be easily confused. However, the exams are moderate in difficulty and definitely manageable. There are labs, where you have to write codes and produce results with a computer. Since the TA's go through the answers almost step-by-step during the discussion, it's hard not to get a nice score out of this, so be sure to attend lab sessions. No homework, but there are online-quizzes, which are similar in difficulty with the examples he goes through in class. In addition to all these, Prof.Tsiang posts his slides and recordings of the lectures to the website, so that if you don't want to walk all the way to the classroom, you can still catch up by self-studying. All in all, an easy-A class, as long as you go to labs and pay attention to the concepts.)

2.[Workload]:★★★★(No homework, but have to do multiple-choice online quizzes which takes about 30 minutes per week. Labs are important, but you can get away with it by attending lab sessions and pay attention to the TA who basically gives you the solution.)

3.[Lecture]:★★★★☆(AMAZING! To be honest, attending Prof.Tsiang's lectures is a kind of enjoyment for me, since he goes through all important concepts so clearly and logically with detailed examples that it is hard not to understand the concepts after the lectures. Also, Prof.Tsiang goes to great lengths to make his classes as enjoyable and resourceful as possible, so definitely go to his lectures even if you can self-study with the notes he posts online.)

4.[Overall]: TAKE HIS CLASS at all costs. Prof.Tsiang's stats10 has been my favorite class at UCLA so far, and I reckon you will feel the same, should you choose to accept him as your professor.

Though I'm only a sophomore, but I'm 120% sure this is the most terrible learning experience in my entire academic career. There is 10 homework in total, all of which are graded extremely harshly (TA Jake has this incredibly strict grading rubric which he refuses to release to the class so you don't know what he expected for homework until the terrible grade is out with tons of comments for the smallest format details). A lot of the homework includes things he hasn't really cover in lectures. He just throws you a function and a brief description for that and expects you to figure out by the help section in r studio (the help section includes EVERYTHING in r, so basically he expects you to know everything because you can self-learn through that help section). He really likes giving out an unmanagable amount of homework and assignments before exams. Before the second midterm, we have three homework dues, one of them is to write 26 built-in functions. That homework takes me around 10 hours to write out functions that could work 99% percent of the situations. But what Jake expects are the most perfect functions that could work for even the most rare circumstances, and in PERFECT format, so I only get 53/100. By the way, he deducts points for using print() function which he thinks it's undesirable. So for one function even mine works perfectly, but I get 2 points deducted just because I use a function which he doesn't like. For thanksgiving holiday, we don't have class on Wed, but mike assigns a whole new chapter for us to self-study. Normally we spend about a week to learn a whole chapter, and mike just expects us to have enough time to self-learn a new chapter because we have one day off prior to thanksgiving. After thanksgiving is week 10, and we have another new chapter to learn, another homework for the new chapter due on week 10 Friday, and a Final Project that is SUPER HARD that takes me over 20 hours to work on which is due at the end of Final week. Mike constantly reminds us to have enough rest and enjoy our life and care about our mental health. This could not be more ironic because this class is the source of all my unhealthy schedule and heavy workload and mental health issues. Mike looks kind and he does act kindly and funny in class, but during his office hour he becomes super cold and intimidating. He never directly answers your questions but instead looking at you with a questioning eyes and ask what do you think. But the thing is if what I think is right, then I don't need to go to the office hour and ask! Jake is even worse. His office hour is a total waste of time. You have to sign up through a link and wait for an hour or so for him to call your name and get not really very useful feedback.
If you are truly in love with R language and are willing to spend every piece of your spare time to work on R , this class is perfect for you. As long as you have time and patience and passion, you can surely learn a lot. Otherwise, this will be the most horrible nightmare in your life.

This class might have been good in the past, but this is definitely no longer the case. I went for multiple office hours but it was one of those instances where he taught you 1+1=2 and then asked you to invent and think of a new color during the mid terms. Do not take this class at all cost - what everyone is saying here is actually true (apart from that one positive comment that is prolly written by Jake). Stay strong my fellow bruins, this class is GPA suicide and avoid it unless you have coded since a tender age of 3. PS: Jake is a spy from USC who's sole purpose is to destroy your GPA.

Professor Mike (as he prefers to be called than his last name) is arguably one of the best professors that I have taken as a lower division class (I took this class for fun for the summer, since it does not satisfy any requirements for my engineering major). Anyway, Professor Mike went above all expectations that I could have expected from any public university faculty member. His lectures are very clear with the content and relatable applications, often amusing with his interesting jokes/comments, and his attempt to connect with the students and himself, through Campuswire and proper communication, is distinct and commendable (in fact, I think he connected with the students on a personal level almost unparalleled than any faculty member I encountered at UCLA). I am satisfied that I took this course over the summer, and it will be an experience that I will not forget for the rest of my life. And also, his Winers-and-Cheese Club (basically, a personal mini social club) was also a very fun experience, being able to chat with him informally. If you want to connect to him on a personal level, this is the place to be (at the time I took his class, it was on Fridays, 7:30 pm, at MS 8105). Dr. Mike, on behalf of the entire body of students that took Stats 10 for SSC 2022, thank you for all that you do! I am certain you will make many more meaningful achievements, both within teaching statistics, researching in statistics, and making long-lasting friends (because waffles and friends come before work, right?).

The grading is not strict and curves are often given. Mike is engaging and clear in his lectures and the posted notes are organized. The content is very interesting to learn and if you pay attention to class and review the notes, you'll be fine with this class! After taking Mike's stats20 gave me the incentive to take more stats classes and probably minor stats.

Mike is amazing. Amazing professor and amazing person. When he tells you that whole grades aren't more important than your health you best believe he means that, it's not just something he says just to say it. During finals week when I got an untimely illness to say that he was accommodating and helpful would be an understatement. If you are going through something reach out to him he is a very caring and understanding professor which is somewhat of a rarity in South Campus. Also a great lecturer, I'm the type to stop going to lecture after Week 6ish but I kept going into Week 10. He really breaks down the material nicely but keeps it light like you leave the lecture not even realizing just how much you just learned. Also, laugh at his nerdy jokes, nobody in my hall did and it was super depressing because they were actually lowkey funny.

The class itself is hard but manageable. Don't go into it thinking it will be easy or even medium. If you go into it knowing that you will have to learn an entire coding language from scratch (which is hard) then you will be fine. How to do well in this class? HOMEWORK, HOMEWORK, HOMEWORK. Don't leave it to the last minute. Don't copy it. Really struggle through it trust me it is better to struggle on the homework than cram before the test. Do it by yourself, not with a partner. Also, do or at least try the advanced problems, they are not required but do it anyway.

The grading is beyond fair, the tests are strictly graded but the curve is generous to make up for it. It is after all, a class rank test which is annoying for other students to have to do poorly for you to look better in comparison but it's as close to fair as course like this can get.

I think somebody in here posted the grading distribution so find that.

I reinforce all reviews before me but would like to correct one thing. The grade distribution did not greatly change so expect a good curve even if the class is failing.

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 )

(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.