What are the major strengths and weaknesses of the instructor?
1. He can communicate ideas very effectively, concisely and in a fun and entertaining manner. One of the best professors I've had at DePaul, hands down.
3. He seems to really enjoy teaching
4. Prof. Reilly does a great job of presenting the material in a constructive and engaging way. I really enjoyed his lectures.
5. The instructor keeps students interested all the time, he can explain difficult topics in very simple way. He is demanding, but also very helpful. The only weakness is he's always late :)
6. Keeps the students interested and engaged. His presentation and interaction with the class is unique.
7. Instructor is very good at presenting the material - definitely one of the more interesting professors I've had
9. The professor does a good job of explaining concepts in a way that people can understand. He also does a good job of not letting the students get the class off topic. He will take irrelevant (or wrong) statements/questions by students offline. However, I felt that sometimes he spent more time on topics than should be required.
What aspects of this course were most beneficial to you?
1. A great introduction to the concept of design patterns
3. Class time
4. The homework assignments were very beneficial. They provided the right amount of challenge in order to learn the various software pattern ideas.
5. I improved my programming skills and changed my way of thinking about it.
6. the home work.
7. Design patterns
8. Learning how to be a more professional developer and write better code.
9. As a professional Java programmer, I was already very familiar with many of the OO concepts taught in the class, however I was never formally introduced to any of the design patterns, so the discussion of the different design patterns was very beneficial.
What do you suggest to improve this course?
1. No much, it's great.
4. Nothing, I thought the course was great.
6. I would strongly suggest "re working" the first three assignments with better more structured code. The code is in a poor state and the subtle differences between the assignments makes the task more difficult than necessary. If the code was "good" with good design pattern used, then we would be exposed to the "right way" to do things from the beginning and that would help reenforce the class concepts. I agree that sometimes (most often?) we will run into bad code in the field, but there's a time and place for learning to deal with that and I don't believe this class is the right place.
8. I don't know. This was a hard class for me.
9. I felt that some of the final project contained too many implementation details.
Comment on the grading procedures and exams
5. Grading system is fair.
7. Exams definitely reflected what was presented in class and were reasonable for what would be expected from a graduate class
9. Grading was fair and prompt. The professor did a good job of explaining the solutions.
3. Bringing a guest lecturer was a good experience.
5. That course is definitely worth taking!
6. Originally I was going to "skip" this class by taking a class that utilizes SE 450 as a prerequisite. I would say that I'm more than a little glad I didn't skip it.
8. He warned us this class was hard and will take a lot of time. He was very right. 10 weeks is not enough time for me to learn all the material in this class. I am going to continue to study patterns after this class ends because I want to internalize that knowledge so I can think in patterns. I was not able to get to that level in the 10 weeks of the class. It was too much info for me.
9. This is only my second class to take at DePaul and the previous class and professor was great, so my rating of this class and professor as average is compared to a high standard, but based upon my experience at DePaul as the question asked.