for Oregon State University's Computer Science Post-Bacc Program
Lower Division
Core Class
CS 271
Computer Architecture & Assembly Language
Filter:
213
Reviews
13
Hours per Week
3.4
/ 5.0 Difficulty
CS 162:
71 times
CS 261:
44 times
CS 290:
19 times
CS 352:
17 times
CS 340:
12 times
CS 361:
11 times
CS 225:
9 times
CS 362:
3 times
CS 325:
3 times
CS 161:
2 times
CS 475:
2 times
CS 467:
2 times
CS 464:
1 time
CS 381:
1 time
CS 391:
1 time
This was such a great class! The course materials and organization are excellent; I’d say it ties with 261 and 340 in that regard. You don’t just learn something one week and throw it away the next. As with anything else, you’ll be better set for success if you start assignments early. Most people will tell you Project 5/6 are the hardest, but I actually spent the most time on Project 4 (with half the time spent on the extra credit, lol). The exams require careful studying but were very fair. The rest of our postbacc classes could learn a thing or two from this class.
Submitted Fri Aug 14 2026
Don't be afraid of this class. Start coding projects early, but they really aren't that bad.
Submitted Mon Aug 10 2026
Don't delay on starting projects, especially the last two. You should absolutely take the Summary Exercises for each module twice, even if you get 100% on the first try. They are the best learning resource in the course.
Submitted Mon Aug 10 2026
I really enjoyed this class. Its very cool getting to learn about what a CPU is actually "doing" (*spoiler alert* all your code eventually is just moving bits between memory and registers then comparing their values.) I took during the summer so I didn't have to take the mid-term or final - but I could see how those might be pretty brutal if they are proctored. I do think the content is shallow in spots, like this could be part of a Comp Arch 1 + 2 series. Project 5 + 6 each took me about 10-15 hours to complete (I have quite a bit of programming experience so ymmv.) You will lose annoying points based on their arcane style guide, its an easy way for the TAs to pretend they actually graded your code. Call them out on it and get those points back.
Submitted Tue Aug 19 2025
Be sure to start the projects as soon as you can to give yourself enough time. I took this class during the Summer term and there was no midterm or final exam. Don't be fooled into thinking this class will be a cakewalk from the first projects. This was my only course for the quarter and it was still a struggle. Attend office hours, utilize the Ed discussions and manage your time well. The class is hard, but doable.
Submitted Mon Aug 18 2025
I found the "assembly" part of the class to be super fun and the "architecture" part to be really dry and horrible - think long readings with quizzes that have questions on things that aren't even in the long readings (although it's open everything - book, notes, Google Search, etc.). Start the projects early - you usually get two weeks for them - and actually learn to use the debugger and you should be fine. One minor annoying point: The projects for a few of the modules were actually assigned the week AFTER you'd do the reading for it - I think so that you could let it soak in - but it often meant that I didn't really understand the readings until after I'd done the project, so in my case, that sort of backfired. But if you're not getting it the first time around, go back after you get more practical experience and see if it makes more sense!
Submitted Wed Mar 26 2025
Give yourself plenty of time for the last two projects
Submitted Sun Jun 23 2024
This class is a grind. The only advice is to start the projects early and to go to office hours when you get stuck. Getting an A is doable. I also would not be scared of the midterm and final. Both actually helped my grade
Submitted Mon Jun 17 2024
Start assignments early and give yourself multiple days.
Submitted Fri Apr 05 2024
Very good class. It's challenging but in a good way. The first couple weeks are a lot of reading and new info, but after that it's more focused on the coding. Projects 1-5 weren't too hard, but I struggled with Project 6, so like others have said start it ASAP. Overall I feel like a better programmer after taking this class.
Submitted Sat Mar 23 2024
Page 1 of 19
Course Analytics was developed for students of Oregon State University's online Computer Science program. The data on difficulty, time commitments, course pairings, and tips have been submitted by real students using this survey. Feel free to add your own reviews if you are a current student! The data is scraped from this spreadsheet.
Course Analytics is an open source project by Nic Nolan.
View the repository on GitHub