THIS IS NOT A COMPUTER SCIENCE CLASS. It's nearly all statistics. This class is terrible and should be avoided. Eskin is an awful professor; he does tell you exactly what you need to know for tests, but he clearly doesn't care about his job and doesn't care if students learn anything or enjoy the class at all. Multiple times he would say in lecture "why am I even here teaching? You guys are gonna forget this all in a few weeks anyway."
Also, we were expected to know Python or R coming into this class. The TA (Michael, the worst TA I've ever had by far) told us in the week 1 discussion that if we didn't know those languages, start teaching ourselves. The homeworks (we had four programming assignments) are easy if you know Python/R, and extremely difficult if you aren't familiar with those languages. Besides those homework assignments, WE NEVER TOUCHED PROGRAMS IN THIS CLASS (and no, they don't talk about Python/R in lecture at all). 95% of the class is statistics and math, which was not what I was expecting (or prepared for).
The syllabus is straight up ignored. The TA consistently showed up 15 minutes late to discussion, and sometimes didn't show at all and forgot to send us a cancellation email. I didn't even know where the office hours were until maybe week 4, just because they never talked about it and didn't put the location on the syllabus.
tl;dr: This class is a pretty easy A but you will not learn anything (unless you're super interested in extremely difficult statistics and can keep up with the professor). There is very little CS involved, and Eskin and the TA don't care about the students at all.

This class is more of an advanced stats class. The math that the professor went through in the lecture is super hard. Python and R are the preferred programming tools. However, I do see some students using C++ and still be able to get full credits on all the assignment. Basically, as long as you understand the math behind the " model" or the "algorithm", the programming assignment is a breeze. TAs and the professor are super helpful if you are willing to talk to them after the class. Though the office hour and the discussion may not be as "formal" as other upper div CS courses (mentioned in other reviews), TAs are always in the Zarlab (in the second floor of MS building) and almost always available. The basic idea is to really let us learn as may advance topics as possible. it's okay if you are not fully understanding the material. TAs don't quite get the ideas sometime. THE GRADING IS SUPER GOOD. Strongly recommended if you are interested in bioinformatic.

Took this class during COVID; the prof and TAs had some weird communication issues where the professor would say something about a due date and the TAs would lag behind a little on getting the news out to all students. They did their best though! Whenever more than a few people asked for an extension, it was given globally to the whole class. Eleazar kept calling these “revolts” jokingly, but they totally were. I don’t think we had a project due until week 6.

All things considered, it was a good class. You learn about genome assembly, resequencing, RNA sequencing in the context of computation. The Stepik homeworks were way more CS heavy than the projects, honestly. They offered a ton of extra credit and lots of cool guest speakers if you’re into research. The projects aren’t that hard and the exams are just there to see if you’re paying attention. If you’re into research/bioinformatics, I’d suggest this as an introductory course. Not too difficult and pretty cool. This is coming from someone who learned Python concurrently with taking this course!

No doubt one of the most enjoyable classes I've taken at UCLA. The TA's are kind and understanding, and the lectures the professor and guest speakers gave are truly inspiring. Overall, I would highly recommend taking this class, regardless of whether you're interested in genetics/biology or not.

I want to preface this by saying I've never written a Bruinwalk review before. That is how negatively I view this course - and I haven't even taken the final yet. If you don't have to take this course, DO NOT TAKE IT. I'm writing this review ASAP so I don't forget about it once I'm out of this course, as I never want to think about it ever again. I know once that final hits, I won't want to look back.

First and foremost, the projects. The projects are INSANELY long and quite difficult. There is no hand-holding; you are ON YOUR OWN. There is some "guidance" but realistically you will be spending 10+ hours on each project, all things considered. Like another reviewer said, even the setup had no explanation. Just starting the projects felt like a massive scavenger hunt. Be ready to dedicate entire days to just the projects alone. They are in a "Part A", "Part B" structure, where each week you get part A, then the next week part B of that project. Part B is typically slightly easier than part A. Following that, you get an entirely new project to start from scratch - completely unrelated! The only "plus-side" to this (if you could call it that) is you get a 48-hour extension on any project, no questions asked, just by filling out their project extension form. You can use this for each project, so in theory, projects each have a two day extension attached. But this doesn't really help when you're getting projects weekly anyway.

Having taken the midterm, I can say it was moderately difficult with a 70% median, and deviated pretty significantly from the practice. Extremely long - I worked until the very last minute. There were certainly some curveballs. I got baited by a previous Bruinwalk review that said the midterm was just like the practice exam. I'm not sure if that was the case before, but it CERTAINLY is not the case this time around. The practice was 4 pages long, with the actual midterm being 20 PAGES.

Speaking of lectures, the first half of the course was quite alright (Eskin), but the second half's lecturer was subpar (Ernst). Eskin was moderately engaging and I actually managed to follow his lectures. Ernst on the other hand, simply cannot lecture. Whenever he walked up there, it seemed like he read directly off the slides. I opted to watch the recordings instead of attend in-person lecture as it was a massive waste of time. That's a plus though - the lectures for this course were recorded. However, they only posted lectures for a given day once the next lecture had already occurred. For example, lectures were on Tues/Thurs. If you missed Tuesday, you would have to wait until Thursday to see Tuesday's lecture - and then wait until next Tuesday to get that Thursday recording.

The homework is essentially a bunch of leetcode problems, with some of them being comically easy, and others being extremely time-consuming - almost project-tier. There were 7 of them, so you can imagine how that piles up on top of the crazy weekly projects.

TL;DR: Project-heavy, long and tedious exams, recorded lectures (delayed), heavy workload. Just a difficult course overall that does not feel rewarding to take.

Took this class for my Bioinformatics minor. This class is taught by two professors together: Prof. Eran Halperin and Prof Eskin. Honestly, this class is a mess.
1. Lecture. In the first few weeks, the two professors were teaching together during the lectures. As a result, the lectures became very unorganized and confusing, because they often got confused about which was the next slide or what concept to go through next. They also attempted to interact with students by asking questions. Obviously this didn't work out, because it would take at least 5 mins for someone to break the awkward silence and answer the question, then they'd spend another 10 mins going back and forth with the question if the answer was not what they wanted. I went to the lectures for the first 3 weeks, then decided they were purely a waste of time and stopped watching them.
2. Homework. There were no exams, so your grade solely depends on your hw. There were 7 hw in total, each of them contained 2-3 questions. 3 of the 7 hw contain coding questions, and you'll need to know Python or R to do them. The homework are not hard, each should take around 1-2 days. Be careful with the multiple-choice questions though, they don't give partial credits on these questions, and you could easily lose 30-50% of points if you got them wrong. I'll recommend checking your answers with a study buddy before submitting.
3. Discussion. The TAs went through the concepts and algorithms required for hw during their discussions. After the third week I stopped going to the lectures and used discussions only to do my hw, and I got full scores on most of them. Shoutout to Jingyuan for being an amazing TA. She explained everything clearly, and gave a lot of helpful advice during her OH.
Overall I don't recommend this class. The workload was not high, but I felt I learned nothing. The lectures were too disorganized to learn anything useful.

I haven't even finished this class yet, but I feel the need to write a scathing review so that all possible future students know, DO NOT TAKE THIS CLASS IF YOU DO NOT HAVE TO.

Every week is assignment after meaningless assignment. We had homework, a project, and a mandatory guest speaker lecture + discussion assignment THE SAME WEEK as our midterm. The homework assignment was so poorly designed that only 3 people were able to solve the last coding problem due to a memory limit issue, so all of us apparently just wasted our time on an unsolvable problem right before the midterm. Mind you, there are project deadlines every single Friday (at noon for some reason), so all of this came after a horrendously long project designed to have at minimum a 30 min-1 hour runtime. How can we reasonably iterate on a project if it takes the whole day just to test it a few times? I think the entire class had to use AI on it, and the average was still a 60% because of how impossible it was. I had to run it overnight and force my computer not to sleep.

The midterm also was 20 pages long and significantly harder than the practice midterm, which was only about 4 pages long. Many concepts were not mentioned a single time in class, only in discussion. The professors were also whispering to each other the entire time and kept picking up phone calls, which many of us found to be disruptive and disrespectful to the students.

They also enforce mandatory participation at least once with both professors, so everyone participated once and never showed up to lecture again because we don't learn anything efficiently. Eskin is not able to get through a single sentence without stuttering and ending it incompletely.

Another sign that the professors don't actually care about the student experience is how disorganized the assignments are. Not a single deadline is posted except for deep into the Lecture 1 slides, so every time I need to check when something is due, I have to scroll about 50 slides in. Additionally, NOTHING is explained by the project instructions. It was extremely hard to get started on Project 1 because the instructions did not even specify that it was a coding project, let alone where to find the files that we needed to work with. I had to deduce that I was supposed to go to the files tab and download the project zip, then write a python script to produce the answer file. Finding out what the project was took longer than actually doing it. They also do not mention at all where to submit projects in the specifications. I have to scroll through all of the BruinLearn announcements to find the submission link every week. Is it that hard to include basic instructions, the deadline, and submission link in the project instructions? Any of us could organize this class better.

This class is hard to be hard. They want us to feel like it's a challenge, but they do it by assigning a load of assignments and enforcing arbitrary requirements rather than making it a challenging intellectual experience. DO NOT TAKE THIS CLASS.

Super cool class if you're interested in the real world application of algorithms, even more so if you have a budding interest in bioinformatics. In each of the projects, you implement industry standard tools from scratch, which is super rewarding but challenging. There's no "dumbing" down going on in any aspect. The class has a large breadth and being familiar with CS180 concepts such as dynamic programming is really helpful. HWs were a few easy to medium LeetCode style problems, around 2-3 hours max. The real issue in this class are the projects. Not only are they insanely hard and time-consuming (although they do get easier throughout the quarter), the specs are super sparse and unhelpful. Constantly need to go to office hours to get clarification and direction. First two projects probably took me about 15 hours each. Exams are ridiculously easy though, almost identical to the practices they give out. Lectures are pretty useless. Textbook is surprisingly amazing, being incredibly readable.

Even though it was one of the most time-consuming classes I've taken at UCLA, learnt so much and got a lot of exposure in the industry. Would definitely recommend to anyone who likes algorithms!