CS 3240

I can't tell if Horton is a bad teacher or he just teaches bad classes. We didn't get homeworks back until almost the end of the course, the homeworks had almost nothing to do with the lecture material, and lectures put you to sleep.

This class is really necessary to get a job, yet I don't think it teaches you much of anything except how to hate group work and despise formal software development. On the bright side, at least it's in agile

This class is a joke. No one every pays attention and you can survive the exams by cramming the night before. There are only like 4 assignments the entire semester. The final project is easily doable. If you want a good grade, do well on the project.

Horton seems to think this class is all that and a bag of chips, but it isn't. It may look good to employers who don't know anything about dev shops, but this class is a disgrace to legitimate development companies.

It's a Horton class, so obviously grades were not really relevant to the course until the last two weeks, when we got all the grades from the semester back.

This class didn't seem productive. It seemed like everything related to software development that we learned, we could have easily picked up on the job or from Google. This class was a good opportunity to learn how to use Python, however.

The in class lectures had basically nothing to do with the project, which was 45% of the overall grade. I honestly had no idea how a lot of our project worked, but I was in a group with a couple of really experienced people who knew what they were doing, which helped a lot. Obviously don't be the kid that does nothing for a group project, but try your hardest. The tests weren't that difficult - mostly based of the lectures, and a bit of reading for the first one. He records all his lectures and posts them, so you can play them back to you in double time to speed through the entire semester to review for the final. It's not a hard class, but the project can be frustrating.

Professor Horton is easily one of the nicest professors out there. He's a decently solid lecturer, although the content can get a little dry for this course. I wish Horton taught more interesting classes, since I'm sure he could shine then.

But anyway, this course is unfortunately pretty dry. Horton tries his best to make it interesting, cracking a joke or two every class, but it doesn't really help the way the class is set up. Definitely make sure to actually try to make an effort to learn somethings, as some of the content taught is really important, as Agile practices are actually used in the working world.

The content of the course includes Agile practices, some parallelism, testing, and other software tools (though we didn't actually get to talk about Git). The class had 4 homeworks, which took forever to return as per usual Horton. Two in class tests and a final, which weren't too difficult if you review the slides for the class. Then there is "the project" which is done is groups of 4. You use agile practices to plan out your project, and work through each sprint throughout the last half of the semester.

Overall, the class is important, but boring, and right now, is just one of those classes you have to get through. If they reworked the way the class is set up, it could be a really fulfilling class.

Okay the class is pretty boring. BUT I KID you not you should go to the lectures and pay attention!

It covers design patterns/agile methodology/other important software engineering concepts.

I feel like if I paid more attention to this class despite its dryness it would've helped with my work as a software engineering intern.. a lot.

This class is not too difficult, although the semester project can become difficult at times, especially without proper direction from the course and TAs. Horton is a good instructor, and I would certainly recommend this course for anybody who wants to program as a part of their career.

Class is pretty dry and people don't pay attention, but Horton is really nice and a good instructor. As another poster hinted at, while the material can be kind of boring at times, it may be genuinely useful in practice.

Honestly, fuck this class. It's not even the end of the Fall semester and it's high time I railed on this class. Chances are that at least 2 of your group members know jack shit and won't be able to contribute to the project. The project is too big for one or two people to finish, and Horton changes the requirements up until about a month left in the semester. The most worthwhile part of this class was the 3 weeks we spent learning Python. I can tell you the assignments right now: We implemented a custom Set class and we worked with pycrypto to encrypt and decrypt text files. Dictionaries, lists, and other stuff can be learned straight from the python docs. Learn Python on your own.

Now, this is a required class for BSCS majors. Fuck that too. You can learn all of the worthwhile material by getting an internship over the summer. This class tries to act like a real world simulation of an Agile project. This is impossible to accomplish in a class setting where Horton implicitly relies on 3rd and 4th years who have prior internship experience to carry everybody else.

I go to every lecture and am disappointed each time. I don't even know the grade I'll get in this class, but it most certainly won't reflect the material I have learned and the effort I've put forth in this stupid project. If you are a BSCS major, put this at the bottom of your priority list. Fuck this class, fuck the CS deptarment for making this a required class, and fuck group projects

This class is an extension of the old 2110 - aka it's pointless. Of the 120 students in the class about 30 attended lecture, you walk away from the project learning only what the online documentation tells you, and you won't get any of your assignment grades back until the last possible second (grades are due in SIS tomorrow and a HW assignment due in August still hasn't been graded on Collab). Horton means well, but this class isn't worth anyone's time.