Course Reviews (Responses)
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
TimestampWhat Course Did You Take?How hard was this class?How much time did you spend on average (per week) for this class?What tips would you give students taking this course?When did you take this course?Did You Take a Second Course This Quarter?What Course Did You Take?How hard was this class?How much time did you spend on average (per week) for this class?What tips would you give students taking this course?Did You Take a Third Course This Quarter?What Course Did You Take?How hard was this class?How much time did you spend on average (per week) for this class?What tips would you give students taking this course?
2
8/18/2015 12:10:52
CS 271 - Computer Architecture & Assembly Language
46-12 hoursMake sure you do and understand the self-check exercises after the lectures. The solutions are very helpful.

Study the self-check exercises and weekly summary exercises thoroughly and make sure you can do every problem - all quiz and test problems will be variations of these.

Start assignments early and always try to do the extra credit if you have time. The extra credit is usually either something you'll need for the next assignment or something that will make the extra credit for the next assignment easier and you'll want all the points you can get in this class.
SU 2015YesCS 340 - Introduction to Databases20-5 hoursEasy class, especially if you've had exposure to SQL before. Project can be time-consuming but isn't overly difficult. It helps to have some experience with HTML and PHP before taking this class.No
3
8/18/2015 13:02:30
CS 271 - Computer Architecture & Assembly Language
413-18 hoursSU 2015YesCS 261 - Data Structures36-12 hoursNo
4
8/18/2015 13:18:06
CS 271 - Computer Architecture & Assembly Language
46-12 hoursDo NOT overlook the practice exercises provided with each lecture. If you can understand these without any help, you will be golden. SU 2015No
5
8/18/2015 14:23:38CS 225 - Discrete Structures in Computer Science36-12 hoursBrush up on your algebra if you haven't taken a math class in a while.SU 2015No
6
8/18/2015 17:04:36CS 340 - Introduction to Databases10-5 hoursGood choive for short summer session. Very light workload. Get started on final project early. Prepare to supplement course lectures with material from the web.SU 2015YesCS 271 - Computer Architecture & Assembly Language46-12 hoursProctored tests are very difficult. Assignments start off easy, but the last few can be very time consuming. Study the weekly self-checks and the summary exercises to do well on the proctored exams.No
7
8/19/2015 13:15:30CS 161 - Intro to Computer Science I418+ hoursIdeally come into 161 with prior programming experience. If not, be sure to do the readings and watch the lectures. Doing the programming challenges at the end of each chapter in addition to the homework really helps with solidifying the material as well.SU 2015No
8
8/19/2015 21:42:38CS 261 - Data Structures36-12 hoursWatch the lectures before doing the worksheets and assignments, often part of the answers will be presented.SU 2015No
9
8/20/2015 7:01:21CS 161 - Intro to Computer Science I36-12 hoursDon't procrastinate!FA 2014YesCS 225 - Discrete Structures in Computer Science30-5 hoursGet ready for induction it's probably the most difficult topic in this class. And brush up on algebra it should be second nature.No
10
8/23/2015 17:44:19CS 161 - Intro to Computer Science I36-12 hoursMy advice would be more relevant for students coming in with programming experience -- don't underestimate the first exam! It sounds silly, but without intending it, I had become really used to letting the compiler fix my errors for me. When it came time to do the test, where no compiler was there to catch my stupid errors for me, I was ill prepared and did much worse than expected.SU 2015No
11
8/23/2015 22:46:17CS 225 - Discrete Structures in Computer Science20-5 hoursJust do all the work.SPNo
12
8/25/2015 18:55:42CS 161 - Intro to Computer Science I313-18 hoursGet ahead on the readings. Put the time in to understand the basicsSU 2015No
13
9/10/2015 13:20:58CS 352 - Introduction to Usability Engineering113-18 hoursKeep communication with your group members, even if there are no assignments due in given week. Also, the final (during the summer session) was comprehensive and is mostly written. I would get fluent enough in the material to answers 25+ short-long answers in 110 minutes. It did not feel like enough time! SU 2015YesCS 261 - Data Structures213-18 hoursI would listen to the lectures to understand the content, skim the provided readings (don't waste your time like me) and get another Algorithms/Data Structure book to supplement. Also check out this site... http://visualgo.net/ . The worksheets were 85% helpful for me, a lot of times our group would actually meet in real time through Gchat to do them, it was pretty fun. YesCS 271 - Computer Architecture & Assembly Language418+ hoursIn the summer session the final was a bit tricky. I went into the final with an 88.5 (I was so proud of my grade). I studied really hard, made a superb cheatsheet and felt pretty confident / ready (just wanted to get it over with) going into the final. The final is rigorous in the sense that there were way too many questions for the time allotted. And, (perhaps I was burned out) the wording of the questions were like riddles(literally contrapostives and vague wording left and right! ). I ended up getting a B- in the class, I am still really proud of my grade!
14
9/11/2015 14:48:03CS 261 - Data Structures26-12 hoursHave the worksheets out while you watch the lectures and fill them in as you go. Use the group worksheet time to solidify your understanding.

SU 2015No
15
10/7/2015 2:47:30
CS 271 - Computer Architecture & Assembly Language
418+ hoursExams are tough - don't underestimate them. Get a calculator that does the conversions for you. SUNo
16
10/10/2015 22:43:33CS 161 - Intro to Computer Science I16-12 hoursWI 2015YesCS 225 - Discrete Structures in Computer Science16-12 hoursPractice makes perfectNo
17
10/10/2015 22:45:27CS 162 - Intro to Computer Science II16-12 hoursVery easy, somewhat similar to CS161SP 2015YesCS 261 - Data Structures213-18 hoursTests are pretty hard, and what ultimately ruined my A.No
18
10/10/2015 22:46:33
CS 271 - Computer Architecture & Assembly Language
213-18 hoursSU 2015 YesCS 352 - Introduction to Usability Engineering16-12 hoursA good group/group leader makes this class much easier.No
19
11/13/2015 11:57:59CS 261 - Data Structures413-18 hoursMake sure your algebra is down well. Go through the practice quizzes and study previous semester's homework solutions. Use alternate resources beyond the required reading. FA 2015YesCS 161 - Intro to Computer Science I413-18 hoursThe first few weeks start off really easy and then it starts escalating with classes, arrays and pointers. Make sure you get the fundamentals down really well as everything builds upon the previous unit. Take time designing what your code will look like before jumping into the actual coding! No
20
11/13/2015 19:44:00CS 225 - Discrete Structures in Computer Science413-18 hoursStudy your algebra and get a head start on proofs!FA 2015YesCS 161 - Intro to Computer Science I16-12 hoursTake an intro to programming class on EdX or Coursera in any language and you'll be set.No
21
11/13/2015 23:42:19CS 161 - Intro to Computer Science I313-18 hoursSU 2014YesCS 225 - Discrete Structures in Computer Science46-12 hoursNo
22
11/14/2015 4:25:54CS 340 - Introduction to Databases20-5 hoursThe final project is the only real assignment in the course. Everything else is fairly simple. Don't get lulled into a false sense of laziness. SU 2015No
23
11/14/2015 10:48:39CS 161 - Intro to Computer Science I46-12 hoursSP 2014No
24
11/14/2015 14:25:27CS 261 - Data Structures36-12 hoursSU 2015YesCS 271 - Computer Architecture & Assembly Language513-18 hoursYesCS 352 - Introduction to Usability Engineering26-12 hours
25
11/16/2015 12:41:57CS 325 - Analysis of Algorithms513-18 hoursFA 2015YesCS 340 - Introduction to Databases20-5 hoursNo
26
11/26/2015 18:00:01CS 161 - Intro to Computer Science I20-5 hours
Pay attention to details. Grading is done by running scripts. Points will be lost for simple mistakes like extra spaces etc.
SuNo
27
11/26/2015 18:02:34CS 162 - Intro to Computer Science II20-5 hours
Don't spend too much time trying to figure out what the instructor wants, just do what makes sense and explain it in the reflections document.
FA 2015Yes
CS 225 - Discrete Structures in Computer Science
30-5 hours
She gives guides, use them. Many of these questions will be on the tests.
No
28
11/26/2015 20:28:43CS 162 - Intro to Computer Science II30-5 hours
Do NOT wait until the last day to do the labs. Don't get hung up on details just make sure to satisfy the requirements for the assignments. The tests are unproctored but only 15 mins for 20 questions.
FA 2015Yes
CS 352 - Introduction to Usability Engineering
20-5 hours
This class is super boring and a chore to do the projects/assignments. Just pray you end up with a good leader and group.
No
29
11/27/2015 5:48:44CS 161 - Intro to Computer Science I36-12 hours
I would say this class is medium difficulty (fairly easy if you have previous programming experience, possibly difficult if you don't). I don't feel the class is too bad, but there is a lot of info thrown at you, and you need to know a lot. The projects ramp up in difficulty, with a few easier ones here and there. If you are having trouble, you really need to start them early as lots of people struggle right up to the end - but you never see many people asking questions earlier in the week.

The first exam probably differs a lot from what people expect from a computer science exam, and a lot of people did poorly (learn how to trace code, learn the unusual cases and what type of errors there are). Actually messing with the errors the and warnings the book gives might be good practice. The second exam is a bit more conventional.

The professor's communication is decent, but he neglects to fully answer questions sometimes, and frequently revises assignment requirements halfway through (again, get started early). He is also very inflexible considering this is a course partly aimed at people pursuing a second career.

The book is decent, but has lots of errors. The course notes are helpful, but also have errors. The video lectures were practically unwatchable to me (accent, voice, pacing).


FA 2015No
30
11/27/2015 15:16:41CS 261 - Data Structures36-12 hours
Do not underestimate the difficulty of the tests. Be prepared to write code, answer multiple choice questions, and take the full amount of time allotted to complete the test. The group work can make or break your understanding of the material, so fingers crossed that your group works well together.
SP 2015YesCS 290 - Web Development518+ hours
The old version was brutal. Be glad it's been changed.
No
31
11/28/2015 2:46:23CS 161 - Intro to Computer Science I313-18 hours
The reading was very helpful and doing all of the exercises in the book can help ensure you're grasping the concepts. Figure out a way to learn pointers and referencing. It can be really tricky for many people. Start working on your programs as early as you can.

For the exams, don't be fooled by how easy they seem. For the midterm especially people were really in for a shock. Go back over everything and look at it all again, Practice hand tracing!
FA 2015Yes
CS 225 - Discrete Structures in Computer Science
413-18 hours
Make sure you're up on your algebra. Find a good youtube channel to help you through it. The reading and the videos could be confusing or not great for providing an easier way to understand what you're actually meant to be doing.

Grading on homework seemed haphazard at best. Try to do the example problems in the book while you're reading and as many in the exercise sets as you can.
No
32
12/2/2015 9:56:43CS 161 - Intro to Computer Science I413-18 hours
Plan to have to practice the material on your own. Each new concept should be practiced thoroughly until you have mastery of it BEFORE attempting the assignments. This will allow you to attack the problem with tools you understand instead of learning as you go. Don't be afraid to break things and then go back a fix it. I restructured my bigger programs a couple times each because they sucked my first go through.
FA 2014No
33
12/2/2015 21:04:37CS 225 - Discrete Structures in Computer Science36-12 hours
Practice practice practice! If you aren't good at mathematics, there is no shortcut to get around doing practice problems. The lecture videos are very well done in my opinion, and going back to those notes always helped me. There were always plenty of examples in the book as well.
FA 2015Yes
CS 162 - Intro to Computer Science II
418+ hours
Work hard, work early! Rooker is a weird guy, things are always vague and confusing. If you're confident in your abilities, starting late can be an advantage because you have the benefit of everyone else clearing up the confusion. But, you need to be confident that you'll finish on time. The group work sucks, and the groups are too large for the amount of work that is given.
No
34
12/3/2015 16:06:44CS 340 - Introduction to Databases10-5 hours
The project is the biggest part of this class. Start working on it early and submit the sections for feedback from the instructor/TA. There's a bit of connecting the dots from the lectures to assignments and quizzes, so I referenced the book a little and did used Google searches. I had no prior experience with SQL or PHP before the class. The recommended book also provided a good overview of PHP. I mostly used code from the provided example but the book helped me fill in a few gaps to do some extra things.
FA 2015YesCS 290 - Web Development36-12 hours
If you can find time, create little projects on the side to help reinforce the concepts. From what I hear, it's a lot better than past quarters but there is still a lot of material to cover. Didn't use the book a lot, mostly did searches for online documentation and questions.
No
35
12/8/2015 18:40:58CS 161 - Intro to Computer Science I418+ hours
Class was a bit unorganized - lectures didn't align to the reading very well. If you're new to programming, don't want until due dates to compile your assignments on the school server. Your local environment may work fine despite underlying issues.
WINTER 2014
No
36
12/10/2015 8:57:04CS 361 - Software Engineering I26-12 hours
Take control of your group. The second project took way more time than it should of because a couple of people became foremen rather than teammates.
FA 2015No
37
12/10/2015 16:43:15CS 325 - Analysis of Algorithms513-18 hours
This is a very hard class. The lectures and office hours are bad but worth watching. Read the material. Do the homework. The mid term and final are both hard. Most projects are hard.

You will learn a lot but it will be one hell of a ride.
FA 2015YesCS 361 - Software Engineering I10-5 hoursPair with a hard class.No
38
12/10/2015 18:32:55CS 290 - Web Development218+ hours
Find other resources outside of the class to learn javascript and node.js. I signed up for a udemy course (Rob Percival Build 15 Websites) since it was only $10 when I purchased. The assignments aren't too difficult but definitely get started on them early.
FA 2015No
39
12/11/2015 4:41:21CS 225 - Discrete Structures in Computer Science418+ hoursfa2015No
40
12/11/2015 17:25:02CS 344 - Operating Systems513-18 hours
Start the projects early. The later you do, the more stressful it will be. Every assignment is a long and challenging slog.
FA 2015Yes
CS 352 - Introduction to Usability Engineering
413-18 hours
Be active in your group. Use slack to communicate.
No
41
12/12/2015 10:42:00
CS 271 - Computer Architecture & Assembly Language
413-18 hours
Complete as much extra credit as you can. Start writing "cheat sheets" for each week and you'll have an easier time writing them for the midterm/final. I rushed through the weekly summaries and could have scored better. The lectures are sort of off with the assignments but things started to make a lot more sense to me after the 3rd week. Each point will count towards reducing your stress for the final week where there will be a programming assignment, weekly summary, quiz, and final due so get the easy ones while you can :)
FA 2015No
42
12/15/2015 8:28:57CS 161 - Intro to Computer Science I318+ hours
Start projects early, use the tutoring services often and early if you do not get something. Do all review problems in the textbook to study for exams.
FA 2015Yes
CS 225 - Discrete Structures in Computer Science
118+ hours
The study guides for exams are spot on, make sure to know everything on the study guide. Homework is the hardest difficulty. Quizzes are easier than homework. Exams are easier than quizzes. If you know homework and quiz questions really well you will breeze through the exams no sweat.
No
43
12/15/2015 12:59:26CS 225 - Discrete Structures in Computer Science26-12 hours
Be prepared to use outside resources for better explanations. The lectures are tied to the old book (Rosen) instead of the required book (Epp).
FA 2015No
44
12/15/2015 16:10:52CS 161 - Intro to Computer Science I118+ hoursFA 2015Yes
CS 225 - Discrete Structures in Computer Science
213-18 hoursNo
45
12/15/2015 16:49:45CS 165 - Intro to Computer Science (Accelerated)418+ hours
Understand that this is (most likely) your first taste of CS; chances of that occurring without headaches/stress/worry/doubts are slim to none. You should know the C++ language well enough to get into trouble after this class, various condition statements such as do while loops/for loops/if-else statements/switches/etc, object oriented programming, recursion, pointers and de-referencing pointers, and you MIGHT touch a little on memory management. You should also learn how to debug and how to do it well. Learn how to test as you go.

The key objective in this class is not to become a know it all and perfect at the language. The key is to understand these different concepts. A for loop/while loop/switches/condition statements etc will generally be the same in all languages. They use the same pseudo code and thus are written very similarly. Once you know these concepts, picking up other languages is extremely easy.
SP 2015Yes
CS 225 - Discrete Structures in Computer Science
313-18 hours
This class really isn't that bad. For a person coming in with a non stem background it could be a challenge because a lot of the concepts are...weird. Especially when you get into recursion and Iterations. Make use of the tutors, don't underestimate their ability and worth.
No
46
12/15/2015 16:56:41CS 261 - Data Structures36-12 hours
Just get it over with....I am not impressed with the structure of this class but she is overly fair and wants you to succeed.
SU 2015Yes
CS 271 - Computer Architecture & Assembly Language
418+ hours
This class is one of my favorites in the program thus far (and I am almost done), a lot of people don't like it though mostly because of the assembly language. Embrace it; whether you know it or not, these are your roots as a CS professional. If you played old video games ever, if you have ever installed drivers, if you have ever wondered how the PC and software talk...then those are all answered through low level languages like C and Assembly.

That is also important to note; C will be used heavily from this point on and to debug certain problems in C you will need to know how assembly interacts with the computer.
Yes
CS 352 - Introduction to Usability Engineering
10-5 hours
save this class for a known hard class. Known hard classes are 290/325/372/and potentially 496.
47
12/15/2015 16:56:53CS 261 - Data Structures36-12 hours
Just get it over with....I am not impressed with the structure of this class but she is overly fair and wants you to succeed.
SU 2015Yes
CS 271 - Computer Architecture & Assembly Language
418+ hours
This class is one of my favorites in the program thus far (and I am almost done), a lot of people don't like it though mostly because of the assembly language. Embrace it; whether you know it or not, these are your roots as a CS professional. If you played old video games ever, if you have ever installed drivers, if you have ever wondered how the PC and software talk...then those are all answered through low level languages like C and Assembly.

That is also important to note; C will be used heavily from this point on and to debug certain problems in C you will need to know how assembly interacts with the computer.
Yes
CS 352 - Introduction to Usability Engineering
10-5 hours
save this class for a known hard class. Known hard classes are 290/325/372/and potentially 496.
48
12/18/2015 12:16:15
CS 271 - Computer Architecture & Assembly Language
36-12 hours
DO as much of the extra credit as you can. Do the practice exams as they almost mirror the actual ones. Make sure you know how to figure out memory addresses early. Some programs are easy, some are not.
FA 2015YesCS 261 - Data Structures26-12 hours
This was easier than I thought (got an A). You might want to save this to pair with the tough classes (e.g. I heard 325, 344)
No
49
12/21/2015 11:20:11CS 340 - Introduction to Databases10-5 hours
If you aren't porting over your CS 290 final project as the final project for this class, don't underestimate the amount of time it will take to pick up your backend language.
FA 2015YesCS 325 - Analysis of Algorithms518+ hours
Skip all the lectures and office hours held by the prof. Get all of your lectures from the MIT OCW material. Skim the book, then go to YouTube to fill in the gaps. Don't use Python for the TSP project. If you use the Subtract and Conquer/"Muster" method in place of Iteration for solving recurrences, you won't be marked down on tests.
No
50
12/22/2015 11:29:15CS 161 - Intro to Computer Science I20-5 hoursFA 2015Yes
CS 225 - Discrete Structures in Computer Science
16-12 hoursNo
51
12/30/2015 12:22:58CS 161 - Intro to Computer Science I46-12 hoursStay on top of homework. it is criticalFA 2015No
52
1/5/2016 11:49:38CS 340 - Introduction to Databases20-5 hours
The lectures in this course give you everything needed to succeed. Don't wait until the last minute to do the homework or final project.
FA 2015YesCS 290 - Web Development413-18 hours
The lectures were way more useful than the book. Don't get lulled into a false sense of security the first few weeks. It starts off slow, but the last few weeks were rough. Make sure to understand each new concept, because the final homework is fairly comprehensive.
No
53
1/8/2016 16:09:02CS 290 - Web Development518+ hours
So much new material. Conceptually not bad. Debugging in node can be challenging, and the professors material is relatively thorough. Watch out for The last assignment: database interactions.
Fall 2015Yes
CS 340 - Introduction to Databases
26-12 hours
Fun, simple, not a freebie pay attention.
Yes
CS 261 - Data Structures
413-18 hours
Assignments and worksheets take time, be careful and prepare well. Debugging can be challenging due to longer programs. Significant amount of material covered.
54
1/24/2016 20:19:18CS 225 - Discrete Structures in Computer Science10-5 hoursSP 2015No
55
1/28/2016 20:28:26CS 161 - Intro to Computer Science I36-12 hoursFa 2015No
56
2/6/2016 15:17:50CS 161 - Intro to Computer Science I10-5 hoursSU 2015No
57
2/13/2016 10:47:32
CS 271 - Computer Architecture & Assembly Language
26-12 hoursWI 2016No
58
2/15/2016 17:23:33CS 161 - Intro to Computer Science I418+ hours
Try to get ahead on readings before the course begins. Try to code as many of the review questions for each chapter as you can. Pay attention to the lecture notes, in addition to the textbook.
WI 2016No
59
2/23/2016 14:35:05
CS 271 - Computer Architecture & Assembly Language
418+ hoursWI 2016No
60
2/27/2016 16:04:44CS 162 - Intro to Computer Science II418+ hoursStack Overflow is very helpfulFA 2015Yes
CS 225 - Discrete Structures in Computer Science
26-12 hoursNo
61
3/3/2016 3:01:17CS 161 - Intro to Computer Science I36-12 hoursWINo
62
3/5/2016 17:55:38CS 225 - Discrete Structures in Computer Science36-12 hours
Practice different problems in the book, not just the ones for the homework
WI 2016No
63
3/13/2016 16:16:29CS 362 - Software Engineering II36-12 hoursThe prof sucks. Prepare to google a lot. WU 2016Yes
CS 271 - Computer Architecture & Assembly Language
413-18 hours
Do really well on the programs and you don't need to stress about the exams much.
No
64
3/15/2016 9:43:11
CS 271 - Computer Architecture & Assembly Language
36-12 hours
Don't skip the self-check exercises. The quizzes and parts of the final were directly from them.
WI 2016YesCS 361 - Software Engineering I10-5 hoursNo
65
3/15/2016 11:23:54CS 496 - Mobile and Cloud Software Development418+ hours
Start early and do not waste time. Seriously this stuff will take you longer than you think if you don't have prior experience.

I'm a very successful student in this program and this is one of the most intensive courses I've taken in terms of project requirements and self learning. My family feels like I've been gone for a few months because I've spent multiple evenings and weekends shut-in to my office.

Prepare to teach yourself. A lot. Even you have a question for the instructor, don't wait to ask it. He sometimes can take days to answer on Piazza. Send emails. This feels less like a "learn-about-a-topic" course and more like a "prepare-you-for-the-real-world" course.

Good course with good "real-world" usefulness but not easy like many others.
WI 2016No
66
3/15/2016 11:36:02
CS 271 - Computer Architecture & Assembly Language
513-18 hours
Even if you get a perfect score on a summary, go ahead and take it a second time. You'll get a second set of questions that will be different from the first set of questions. The quizzes and midterm/final are largely made up of questions that are pulled from the summary exercises.

Start the programming assignments early.
WI 2016YesCS 361 - Software Engineering I10-5 hours
This class is largely focused on group work. Be a good group member, and it's an easy A.
No
67
3/15/2016 12:54:16CS 290 - Web Development36-12 hours
This class starts off at a very easy pace, especially if you are familiar with web development at all. The last two assignments take up SO MUCH time, from general feedback this term about 25-35 hours apiece. Make sure you get an early start on them, as the first 8 weeks do not prepare you for this work load. Otherwise a great class, I learned a lot!
WI 2016Yes
CS 352 - Introduction to Usability Engineering
10-5 hours
Make sure you put some thought and effort into your group project and follow directions, as grading on that can get a little picky. It's easy to slack because the rest of the class doesn't require much work or complex thinking. Watch out for trick questions on tests and quizzes.
No
68
3/15/2016 14:40:48
CS 271 - Computer Architecture & Assembly Language
36-12 hours
Stay on top of your work. Do the weekly check exercises that accompany the lectures, since they will be the format of the weekly summary checks, the quizzes, and the midterm/final. I found that most homeworks took me between 5-10 hours. The practice midterm and final were representative of the actual exams. Use the discussion forums to ask questions often!
WI 2016YesCS 261 - Data Structures36-12 hours
The group work is mostly useless. The "book" for this class is a joke. I'll be planning to take a free online data structures course to brush up, because this class fell really short in terms of making me feel like I could go into an interview. The homework code feels hobbled together, and often contradicts itself. Be sure to keep current with the discussions on Piazza because many people will hash out the issues ahead of time.
No
69
3/15/2016 16:33:25CS 344 - Operating Systems36-12 hoursSP 2016YesCS 361 - Software Engineering I10-5 hoursNo
70
3/15/2016 17:17:55CS 225 - Discrete Structures in Computer Science30-5 hours
Quizzes are posted on Thursdays and due Sunday nights. Homework will not be graded by the time you do the quiz, so look at the homework solutions. Exams and quizzes are pulled directly from homework!
WI 2016YesCS 290 - Web Development413-18 hours
Starts slow but the curve sharply increases quickly after the second week. Do each of the activities at the end of the modules, as they are usually the weekly assignment broken up into increments, so if you go through all of them to the end, your assignment is 90% done. Last homework assignment is a BEAST.
Yes
CS 271 - Computer Architecture & Assembly Language
26-12 hours
Read the summary exercises, as they are pretty much exactly what is on the weekly summaries and quizzes. Midterm was taken from quizzes. Get a calculator that can translate back and forth between bases; you should know how to do it yourself, but you do NOT want to waste time calculating back and forth or risk making a mistake.
71
3/15/2016 17:54:59CS 361 - Software Engineering I30-5 hours
Take it with a course that's front-loaded. 361 has two projects. The second project is a big group project with 5 other people. There's a LOT of coordination and group management needed and that's really the key to this class: handling the group stuff well.
WI 2016YesCS 325 - Analysis of Algorithms513-18 hours
The first 5 weeks are incredibly hard. The tests are hard. The homework's hard. The projects aren't too bad. I recommend using Python for most of the projects. And the lectures are pretty bad; use your google-fu.
No
72
3/15/2016 20:01:37CS 161 - Intro to Computer Science I16-12 hoursWI 2016No
73
3/16/2016 7:50:12CS 162 - Intro to Computer Science II36-12 hoursWI 2016Yes
CS 225 - Discrete Structures in Computer Science
30-5 hoursNo
74
3/16/2016 8:59:06CS 225 - Discrete Structures in Computer Science36-12 hours
Don't bother with the lectures, skim the readings, do as many practice problems as you can. Make sure to be prepared for the quizzes each week.
WI 2016Yes
CS 352 - Introduction to Usability Engineering
10-5 hours
Don't wait until the last minute for the group assignments.
No
75
3/16/2016 10:17:15CS 162 - Intro to Computer Science II36-12 hours
It seems overwhelming at first but it is not bad! They throw you into the deep end but it is not unmanageable. Get ready to use google, stack overflow, and other resources all the damn time, because unlike 161 you pretty much are on your own as to how you implement things. You *will* need resources beyond just the book.

Rooker seems like a fucking oddball at first but he's really not that bad. Don't hold it against him. He is really really bad at communicating clearly - get ready for confusing assignments and test questions. Roll with it though.
WI 2016Yes
CS 352 - Introduction to Usability Engineering
10-5 hours
Don't be dick to your group mates. Be a good member and get your shit done. The class is easy, as is the project. You just have to slog through it (if you find it as painfully boring as I did, you might enjoy it).
No
76
3/16/2016 10:57:20CS 162 - Intro to Computer Science II26-12 hours
Get ready to be busy as fuck...lots of busy work. Weekly labs, biweekly assignments, biweekly group projects. Concepts aren't difficult though.
WI 2016Yes
CS 271 - Computer Architecture & Assembly Language
26-12 hours
Not as difficult as most people lead you on to believe.
No
77
3/16/2016 10:58:43CS 162 - Intro to Computer Science II513-18 hours
Pace yourself. I feel as if I learned a lot, but most of the learning came from Stack Flow and You Tube Videos which is both a good and bad thing and probably a contributor to why you had to spend a lot of extra time on this course.
Winter 2016No
78
3/16/2016 12:13:46CS 162 - Intro to Computer Science II20-5 hoursDon't rely just on the lectures. Learn the topics from outside sources. WI 2016Yes
CS 271 - Computer Architecture & Assembly Language
513-18 hours
Watch all lectures and take a lot of notes and do the reading. Coding projects are not too bad but can be difficult if you get stuck since there is pretty much no information outside the book and whats covered in lecture. Midterm and Final are pretty intense but if you spend a lot of time making your note card, you will be OK
No
79
3/16/2016 18:53:01CS 340 - Introduction to Databases20-5 hours
Study PHP early. The database work and relational algebra work is so light you get apathetic until the final project. At that point, you have to learn the language from scratch while trying to make a project work. On the final project, get started (even just with planning) as soon as possible.
WI2016YesCS 361 - Software Engineering I20-5 hours
Pick a vision statement for Project A that you like, and pick a vision statement for Project B you could see yourself actually writing. If you end up as a client (a group picks your statement) don't be a dick by being picky and demanding. Know that Project B is a class assignment about learning Agile, so define the goal end product but don't get demanding on platform or tech. If you ask for a mobile app but the group doesn't know how to make one, they can't spend time following the agile process when they're frantically trying to learn enough about mobile dev in a 2-3 week period to make your stupid app. 40% of project B is delivering "substantial working code". Don't be a dick.
No
80
3/16/2016 22:14:01CS 165 - Intro to Computer Science (Accelerated)26-12 hoursWI 2016Yes
CS 225 - Discrete Structures in Computer Science
20-5 hoursNo
81
3/17/2016 2:04:15
CS 271 - Computer Architecture & Assembly Language
413-18 hours
Read the book. Don't skim it.
Read everything. Also master the self check exercises for every lecture. They are there for a reason and if you understand those then you'll be good when the time comes for the exams.
WI 2016Yes
CS 340 - Introduction to Databases
36-12 hours
Start your project early because it is pretty time consuming. Also dont feel bad if you're not understanding sql right off the bat. I didn't really understand it until I made my own queries with the project.
No
82
3/17/2016 8:16:45CS 162 - Intro to Computer Science II413-18 hours
Starting out this class is very daunting, don't let it dissuade you, just break down the problems into smaller manageable pieces.
If lab 5 is still the doodlebug lab make sure to start immediately, it was disproportionately harder than any of the other labs.
WI 2016Yes
CS 352 - Introduction to Usability Engineering
10-5 hours
The key to this course is having a group where everyone participates, if you have a good group you shouldn't have to spend more than 4-5 hours a week on the material.
No
83
3/17/2016 10:50:37CS 162 - Intro to Computer Science II36-12 hours
Prepare for pain and suffering. The first assignment is probably the worst, but the general poor quality of the instructor makes aspects of this class a giant pain in the ass. TAs seemed to routinely grade based on their view of what the assignment should be, rather than what the actual requirements were as laid out in the assignment. The group work is poorly structured (too many people, too easy for free riders). Overall the class isn't hard, but it is a decent time commitment some weeks.
WI 2016Yes
CS 225 - Discrete Structures in Computer Science
26-12 hours
Bone up on your algebra before taking this class and make sure you're familiar with summations.
No
84
3/17/2016 14:05:37CS 344 - Operating Systems418+ hours
Practice a lot. The concepts all seem very simple and easy during lectures and notes, but when you need to facilitate them into larger code it becomes complicated and potentially confusing.

Have a decent grip on C coding at the very least.
WI 2016Yes
CS 340 - Introduction to Databases
26-12 hours
The class is not terribly difficult with the ability to take quizzes unlimited number of times. Just practice your queries early and often. Play around with it a lot. Start on your final project as soon as you feel comfortable as having it done 3 weeks before deadline was a huge boost to my time.
No
85
3/17/2016 23:00:18CS 290 - Web Development26-12 hoursRead head and managed your time towards the end of classWI 2016Yes
CS 340 - Introduction to Databases
20-5 hours
Dont do the final project all at once. Spread it out in to chunks and get the free feedback.
No
86
3/18/2016 18:30:36
CS 271 - Computer Architecture & Assembly Language
40-5 hours
The concepts are new to many people - if there's anything you don't completely understand, be sure to clear it up by asking questions on the forums or with the TAs, because you need to really understand the concepts to do well in the course.
WI 2016No
87
3/18/2016 18:49:45CS 161 - Intro to Computer Science I26-12 hours
Read the book and practice writing lots of code both in an ide and away from the computer.
WI 2016No
88
3/19/2016 16:03:26CS 361 - Software Engineering I26-12 hoursWI 2016YesCS 344 - Operating Systems318+ hours
Very time consuming. Start early. Otherwise not that difficult. Some annoying technical minutia, but exam is open book which is nice.
Yes
CS 362 - Software Engineering II
26-12 hours
Professor is difficult to understand. Little useful feedback. Overall easy.
89
3/19/2016 16:04:45CS 372 - Intro to Computer Networks313-18 hours
Socket programming coursework is challenging. Otherwise on par with average coursework.
WI 2016No
90
3/20/2016 2:32:08CS 372 - Intro to Computer Networks418+ hours
Start assignments as soon as possible. Choose at least C or C++ for your first assignment as you will have to use one or the other on your second assignment and it will make your life a whole lot easier. If you can get through the summary exercises you can get through the midterm. The final is a slightly different format.
WI 2016Yes
CS 340 - Introduction to Databases
26-12 hours
Overall everything is easy. Only work with someone on the group project if you have a strong feeling they will pull their weight. The group project can be as time consuming as you make it, but having a helpful partner helps a lot.
Yes
CS 361 - Software Engineering I
36-12 hours
Estimating time spent for this class is difficult. I spent minimal time on this until the group project at the end. Be adamant that your group uses languages/frameworks that the majority are comfortable with.
91
3/20/2016 2:40:08CS 325 - Analysis of Algorithms46-12 hours
Highly mathematical...depending who you are that could be a very good or bad thing.
WI 2015No
92
3/20/2016 16:24:43CS 261 - Data Structures46-12 hours
Do the worksheets as they really help with the programming assignments and, more importantly, with understanding the concepts.
WI 2016Yes
CS 271 - Computer Architecture & Assembly Language
36-12 hoursDo the extra credit if you canNo
93
3/21/2016 17:55:25
CS 271 - Computer Architecture & Assembly Language
313-18 hours
Class is really well laid out. A lot of material to learn but very manageable. Tip: make sure to work through the lecture checks.
WI 2016Yes
CS 352 - Introduction to Usability Engineering
26-12 hours
Stay on top of the schedule for the project parts and reference the examples provided in the class resources section in Canvas.
No
94
3/21/2016 20:12:33CS 290 - Web Development26-12 hours
Each assignment is graded equally but the class difficulty spikes. Make sure to collect easy points at the beginning to help the end. There are trendy technologies. This class is best suited for the over-achiever. You can loaf and do well.
WI 2015Yes
CS 340 - Introduction to Databases
20-5 hours
This is an easy class. 60% of your grade will be determined with the Final and Project so make sure to plan accordingly.
No
95
3/22/2016 11:41:38CS 344 - Operating Systems46-12 hours
Start the programs early. You'll get 2-3 weeks to do each program, but don't wait until the last weekend! There is a lot to the programs, but they're not necessarily very difficult, just time consuming. Final exam is open everything and not too difficult. There is no midterm.
WI 2016YesCS 361 - Software Engineering I10-5 hours
Coordinating the group projects can be difficult. Make sure to communicate early and often. No Midterm. Final was easy if you make sure to study the starred slides.
No
96
3/22/2016 11:54:35CS 161 - Intro to Computer Science I46-12 hours
Practice hand-tracing skills early on. This will be important on the exams. Be careful not to rely on your programming software too much for error messages. The exams will try make sure you know the exact syntax and "punctuation" exactly. If you rely too much on your compiler to tell you what you did wrong you will not do well on the exams.

Also, begin your homework as soon as possible. Do not wait until the last minute because programs may be surprisingly difficult and time consuming. You don't want to be caught having to submit partially working code because you ran out of time.
WI 2016Yes
CS 225 - Discrete Structures in Computer Science
36-12 hours
This class isn't particularly difficult unless you struggle with grasping abstract concepts when it comes to logic. Mostly I found that it was time-consuming. While the work was not tough most of the time, doing all of the homework was tedious and took the better part of a weekend day to complete the homework and quiz for the week. I would suggest not procrastinating and spreading the work out during the week to make room for any other class you might be working on it or free time.
No
97
3/24/2016 11:58:59CS 261 - Data Structures26-12 hours
Be cooperative with the members of your group. The wording of questions on the exams is a little wonky.
WI 2016YesCS 290 - Web Development46-12 hours
Be prepared to be blindsided the last two weeks by the increase in the amount of time required for assignments. A big problem with this class is that there is no structure. It is possible to have over 100% average on assignments and feel lost when the exam and final assignment come.
Yes
CS 352 - Introduction to Usability Engineering
20-5 hours
Be cooperative and communicate with your group. There is no programming and the content does not present any real challenge, so do not become apathetic toward the individual assignments.
98
3/25/2016 13:39:31CS 261 - Data Structures213-18 hours
This class isn't difficult. Study the worksheets for the midterm and final.
WI 2016Yes
CS 352 - Introduction to Usability Engineering
16-12 hours
This class has a lot of busy work but is also not difficult. Be prepared to do a lot of work if you're stuck with horrible teammates.
No
99
4/29/2016 1:18:55CS 161 - Intro to Computer Science I413-18 hoursStart the assignments early!FA2015Yes
CS 225 - Discrete Structures in Computer Science
413-18 hours
Don't panic during quizzes and exams.
No
100
6/9/2016 2:24:37CS 290 - Web Development36-12 hoursSP 2016YesCS 261 - Data Structures36-12 hoursNo
Loading...
 
 
 
Form Responses 1