Finished the course with an A, achieving a 88.81% (A: 86% and above, B: 76% - 85.9%, C: 66% - 75.9%)
Background:
Bachelor's degree in Computer Science from a university ranked #377 out of 436 National Universities in U.S. News
English is my second language (TOEFL score: 95/120)
1 year of experience as a full-stack developer and 6 months of experience in data analytics
Overall:
This is the sixth class I’ve taken in the OMSCS program, and honestly, it’s been the most frustrating one so far. The course content is disappointing. I don’t even know how to describe it. I signed up for “Data Analytics & Security” hoping to learn the basics of data analysis, how to make data more secure, and how to write solid analytical reports. None of that was covered in the course. I took the ML course in OMSCS, and this class title should be changed to "Intro to R, Python, and ML algorithms" to avoid misunderstandings about the class content.
The assignment instructions are vague and hard to follow. You have to read them multiple times to figure out what’s being asked. It feels like the focus is more on guessing what the instructors want than actually learning anything meaningful. They try to frame the assignments as “open-ended,” but the grading doesn’t reflect that at all, so you’re left completely unsure of how you’re doing or what you’re supposed to be getting out of it.
The TAs in this class honestly have no idea what they’re doing. They respond very slowly and often can’t answer students’ questions. You’re better off searching Google or Reddit than relying on them. The TA group seriously needs to be replaced. If you're too busy with your personal life, then don't apply for a TA position and use "I'm busy" as an excuse.
Lecture Activities (28.78 / 30%): This assignment combines a quiz and a discussion, but don’t be misled by the title. It should be called "homework." The quiz part is easy, but the discussion can be tricky. Some prompts require you to provide actual examples, even though that’s not clearly stated in the instructions. That’s frustrating. You can see the impact in the score breakdown; discussions with these hidden expectations tend to average 80% or lower, compared to those with clearer requirements.
Computing Activities (18.2 / 20%): This coding assignment is worse than anything I did in high school AP Computer Science. It asks students to “explore” and modify code without clear direction or explanation of what’s expected. Many of us ended up confused, and when our exploration didn’t match the TAs’ expectations, we lost points. It’s hard to believe this is a master level class. If the assignment is open-ended, grading should be based on what students submit, not on a hidden rubric. This is also the first time I have submitted a coding assignment as a PDF since high school. Back then, we even submitted .cpp files when GitHub wasn’t popular yet, so this feels very ridiculous. You also have to make sure the margins of the PDF layout fit properly on the page, including the parts from the original layout provided by the TA. If not, they will deduct points for that too.
Project Activities (41.83 / 50%): This section is the worst part of the course, and it counts for up to 50% of the grade. They expect you to write an analysis report, but the course content doesn’t teach you how to do that at all. Fortunately, I had a great teammate who explained what makes a good analysis report and what doesn’t. Otherwise, I wouldn’t have had any idea what I was doing wrong. If your group isn’t clear on the expectations, this part can be extremely frustrating.