way better than smallberg
i was doing so well until the last project
start early

I highly recommend taking just this class by itself since the 4 projects and 4 HWs can definitely take awhile. One really nice perk about taking CS 32 in summer is that the super duper long project is the final project assigned rather than the third one assigned. This works to your advantage because most people (including myself) barely finish the basics of the project but because Ambrosio and the TAs don't have time to finish grading ALL of these super long projects by the end of summer, they give 90s-100s for everyone regardless of how much you finished, boosting your grade a LOT!!

Summer class still has TAs, and I highly recommend going to their office hours because they can literally look over your code and tell you what's wrong with it. You can also just go and see what other people wrote down for their code and more or less copy it. Lectures are recorded with pretty thorough slides so there honestly is no point in attending class tbh.

Taking CS32 during summer was definitely an arduous journey, as the content taught over 10 weeks in regular quarters is compressed within a 9-week course. Would not recommend taking another summer class, or taking part in external commitments, if you wish to do well in this class. Content-wise, it is not too difficult, especially with Professor Ambrosio's lectures and slides that explain the concepts pretty well. If you wish to master the concepts, highly recommend working on the LA worksheets. However, be prepared to spend tons of time on assignments, especially during the last week when you have Project 4, Homework 4 and Final. I enrolled in another summer class and the last two weeks were hell for me. Fortunately, Professor Ambrosio is extremely responsive via Piazza and email, so clarify with him whenever you are in doubt, especially regarding project specs. Though his exams are tough and some questions might not be most clearly phrased, make use of the Zoom session that he holds during exams to clarify any doubts with regards to exam questions - it helps a lot. Overall, CS32 is much more fun than CS31, but you have to put in way more effort to do well in this course. Final advice would be to start working on projects early - do not procrastinate until the night before they're due.

So many people dropped this summer and I thought about dropping too, but I’m glad I stuck through. If you’re planning on taking this course over the summer, make sure it is your ONLY course as the material and the assigned hw/projects get incrementally harder. Especially because this is a 9 week class you are constantly bombarded with new concepts and all of a sudden it’s already the midterm or final. Other than that, just try to aim for above the mean on the exams and a high B to a mid A on the projects and you’ll do just fine as he hands out 10 point of extra credit and curves the final grades generously to a B- average.

I think the class is fairly manageable if you take it as your sole class in the summer. I took CS 31 in previous winter quarter, and did not code at all in the spring quarter which screwed me over for the early parts of CS 32. If you are taking this course for your minor, make sure to either do CS 31 the quarter before or make sure that your coding skills are fresh because CS 32 is a whole league above CS 31. The projects and homeworks aren't too bad IMO as long as you start early. The only struggle in the course is really the last 2 weeks when you are working on the 50 page spec game project, and you have do HW 4 and study for the final at the same time. I will say however that project 4 was graded very generously so don't worry too much if your project isn't perfect. As far as exams go, the first midterm is really the hardest exam (mostly because of timing). The next two exams only get easier and tbh the concepts get easier too. (For me, understanding pointers was the hardest part of the course lmao). Some exam questions were a bit ambiguous, but overall exams were fair as long as you prepared ahead of time (None of the exams are cumulative so it is very easy to prepare). Also, the prof. has a nice policy of replacing your lowest exam grade with the average of the 3 exams. In hindsight, getting an A in the course is very doable as long as you score as highly as possible on the projects + hws, and score around the mean on the exams + you do the extra credit.

Firstly, I definitely learned so much in this class. Professor Ambrosio is truly an amazing professor and person, always open to helping students no matter what the question is, extremely patient, and very knowledgable about CS and the industry. He had a Piazza on top of office hours and contacting him through email, all of which he would reply within 24 hours, and majority of the time just a few hours after you asked the question. He even answered questions on the weekends and treated the weekends like normal school days. Projects, Assignments, and Tests are returned to you in a week, and a lot of the time he starts grading them the day you turned them in. (Although this will probably change since he has a kid on the way!) CS 32 is an insanely tough class, and I feel that the Professor definitely knows that and wants to see everyone, no matter what level you are at with CS, succeed.

I'm sure it would be very different story and the class would definitely be manageable for someone who is familiar with coding big programs and these concepts. However, this class was so time consuming and extremely hard for someone like me who was learning concepts like recursion, inheritance, polymorphism, classes for the first time. Because the class moved so fast, starting around a third of the way into the class, it constantly felt like there was a big test or big project due in a few days. Because of this, I felt like I could barely understand the concepts fully before I had to work on the "next big thing". Towards the end of the session, right about when you finish taking Midterm 2, you really need to be cautious of how you divide your time, since the Final, Assignment 4, and Project 4(which is the 50 page spec Project 3 during the school year) are due the same week. We were literally learning a new concept in class on Monday and the final was that week Wednesday which should give you a picture of how tight on time everything feels in this class.

If you're someone like me who doesn't have much coding experience or familiarity, just make sure you have a lot of time this Summer and no additional big commitments to soley focus on this class and practice the new concepts. I was able to get an A- in the class, despite getting low C's on the first 2 midterms (and feeling extremely defeated), but working hard on the projects, which I got full scores on each. He replaces your lowest score with the average of your Midterm 1, Midterm 2, and Final scores, and I felt that the Final was actually the easiest exam of the three, with much less coding questions and a lot more conceptual questions. This class was also very mentally taxing for me, but just keep going, don't give up, and you will be okay.

There was the tiniest curve for my session (a 0.5% grade boost), since he curves the class so the average is a B-, and our class average was 79.5%. Midterm 1, Midterm 2, and Final class averages were all around a low 70%, C- range.

I'd say this class is the most challenging class I've had so far at UCLA, but it's not impossible to do well in it. The projects are not impossible, but just require a lot of time, while the exams are not insanely difficult, but just require practice and solid understandings of the concepts. Basically, the Professor and class environment never feels like it is "trying to get you" or waiting to weed out half the class since they are beginners at CS and don't have years of coding experience or whatever. Always always clarify any questions you have or ask for help/support from the TAs and the Professor. You can do it! I believe in you!

This class was pretty easy, except for project 4. Project 4 was horrible. I had a solid A before project 4 and then I BARELY finished with an A- after. Start project 4 as soon as you get the spec.

Ambrosio is a good CS 32 professor! he teaches the material well, and he's a pretty cool guy overall. he does often answer questions in a really confusing way on piazza/emails, but when you talk to him verbally he's a lot clearer. the tests weren't super hard imo--there's three in total, two midterms and a final, and I actually thought the first was the hardest one. the homeworks aren't bad either, though projects can be tougher. I needed a lot of help for projects 3 and 4, and even then I didn't really score super high, because after a certain point I just lost motivation to sincerely work on it lol. he gives 10 points of EC max, and substitutes your lowest exam grade with the average of all of them. the thing to remember about this class is that you have to be careful about submissions!!! he is not lenient at all with late submissions, even if they're one second late / submissions via email in case CCLE isn't working, even if you submit it on time / accidentally submitting the wrong file, etc. it's just a flat 0 if you don't get the correct submission in before the deadline, which happened to me oops. but yeah as long as you don't get 0s on anything I do think this class is pretty doable if you're just looking to pass.

Professor Ambrosio is truly one of the nicest and most helpful professors I've had during my time at UCLA. He is incredibly patient and will answer any question you ask, whether it is in Office Hours, lecture, or over email. The tests were somewhat difficult to complete within the given time but were not incredibly easy or difficult. The projects took a huge amount of time, in particular Project 4. Project 4 had quite a lot of requirements, and I wasn't able to finish. The fact that Project 4 was due the same week as the final and has Homework 4 made it even harder to finish, and I would say there were a good amount of people who weren't able to complete it. The rest of the projects took a fair amount of time, but not as long as Project 4. Overall, I found the material of the class to be a lot more interesting than CS 31, and I think I gained a lot of valuable skills in this class.

I didn't enjoy this class as much as I expected, but Ambrosio is a decent lecturer and answered questions quickly on Piazza for the most part. He also graded everything quickly and went through every single one of our submissions, which I imagine would take a ton of time. Given that, he deserves a lot of credit for the time he spent teaching this class.

The material wasn't very interesting to me, and projects were a huge time sink, although that's just CS 32 in general. Project 3 and 4 were placed at inconvenient times during the quarter, and both were challenging and/or took an insane amount of time. Project 3 was difficult because everything had to be done with recursion, and Project 4 wasn't impossible but legitimately took up most of my time the last two weeks of class. Exams had a mix of relatively easy and difficult questions, but a lot of times the wording was just not clear. I spent a lot of time trying to figure out what exactly he meant on some of these questions.