This post is part of an ongoing series recapping my experience in Oregon State University’s eCampus (online) post-baccalaureate Computer Science degree program. You can learn more about the program here.
Six-word summary: Brutally paced pointers pointers pointers pointers
The beatings are over I survived CS162! If you were wondering where OSU’s eCampus computer science weeder course is, this is it.
The material is challenging and the workload is punishing. The video lectures are crap, but the book is good. The class isn’t well organized (expect poorly written assignments with unclear requirements). 10 weeks is nowhere near enough.
However: I learned a lot. I got faster than I ever thought possible and worked with topics I thought would have had their own standalone courses.
In this article: topics covered in CS162, survival guide, what I thought of the class.
Note: While I normally love to post code here, I can’t share any of my project code (against student code of conduct) or specific assignment requirements, test questions, etc.
Topics covered in CS162
The class is taught in C++ and teaches (or at least requires you to know):
- pointers to arrays
- pointers in arrays
- pointers to pointers
- pointers to instances of classes
- passing pointers to functions
- linked lists made of pointers
- abstract class and subclasses
- virtual functions
- overloading operators (give == an exciting new meaning!)
- writing functions that do something recursively, like reverse a string, sum numbers in an array, solve a math problem
- data structures: queue, dequeue, stack, linked lists, circularly linked lists
- sorting algorithms
CS162 is a programming class. Like CS161, I found my Macbook to be sufficient for this class.
I don’t know why they tell people to get a Windows PC and use Visual Studio. I didn’t need it and you won’t need it – there is no assignment based on Visual Studio knowledge.
In fact, judging just by Piazza posts, a number of students seemed confused by the extra files and the “another thing to learn” factor introduced by Visual Studio.
In case you are curious: I did every assignment in Sublime Text and a Terminal window.
At any given time expect to be working on a 1-week lab assignment and a 2-week project, and mid-course, a group project on top of the first two. You will also write a multi-page document (PDF) for each project with a test plan (input, expected outcome chart), your designs, ideas you changed along the way, reflections on the assignment. This document always took me at least 3-5 hours to complete to my standards. There’s a quiz every couple weeks (15 minutes, not proctored).
I’m a proactive student who started each week’s material the moment it was released, worked on it daily, and generally finished just moments before a new load of work was dumped onto me.
The first two weeks hit like a ton of bricks: a simple Langton’s Ant simulation by itself would have been a large assignment, but CS162 adds a user-navigable menu, input validation, user-adjustable parameters (dynamically sized board, variable turns to run, etc.), and other features that have to be designed, coded, tested, debugged.
There are also two lab assignments to complete while you work on the Langton’s Ant project.
This pattern continues until the end of the course. The toughest week was the one where I was working on a project, a lab, and a group assignment all at the same time.
CS162 Survival Tactics
It’s easy to find people complaining online about how disorganized and intense this class is but what I really wanted when I was in the thick of it was some help. (The OSU eCampus CS subreddit is a good place to look for advice on CS162, too.)
Here’s what I did (or wish I’d done sooner) that made CS162 more bearable.
Take it by itself (if you can)
I know there are financial aid reasons not to but if you’re normally taking 2 classes a quarter, consider taking CS162 alone (or at least with fewer classes than you normally would). It’s a ton of complex material – assuming you haven’t worked a lot with C++ pointers, memory, arrays, etc. yet – and the assignments are black holes for time.
Diagram things out on paper
I found many of CS162’s assignments too complex to hold entirely in my brain.
For example, here’s a crazy thing we did: create a circularly linked list (in C++), let the user fill it and delete nodes from it. When you exit the program, it has to unload from memory node by node. “Empty nodes” are marked with -1 for their values. This drawing I made helped a ton (actually, this was probably the 5th iteration of this drawing).
And here’s another one, this one showing how the heroes in the polymorphism project either rejoin the tournament queue or get kicked out to each player’s respective loser pile.
PS: Some people got really precious about their diagrams having to be works of art, but you don’t have to for these assignments. Just draw this stuff out, paper/pencil (or a little whiteboard) is sufficient, and plan to trash your first few drawings. If you need some material to bulk out your retrospective writing assignments for each project, photos of the diagrams you make are excellent fodder.
Go straight to Google (and Stack Overflow, and YouTube)
Sure, it sucks to pay $1880 to do so much self-teaching but you’ll get a lot of mileage out of the skill. The recorded lectures are crappy and I felt like they were wasting my time. There are better guides to all of the concepts covered in this class on YouTube.
Buy the book
Here’s the book on Amazon: Starting out with C++ Early Objects
I recommend getting a physical copy so you can have it open next to your computer while you work, and use your monitor(s) for your code and Stack Overflow. It’s the same book you use for CS161 (if you haven’t taken that yet, either), so at least you get two classes out of it. You can also buy the loose leaf edition to save some cash.
After two classes with it I can say it’s a good book. The examples are relevant to the coursework, they’re clear and easy to understand, and there are a good number of examples.
Start every week’s material the day it drops – and don’t count on weekends
Sometimes the new week will be released on a Friday. Sometimes a Saturday. Sometimes a Sunday! And no, the instructor doesn’t move that week’s deadline out just because you lost the weekend due to the materials not being released in a timely manner.
For this reason, I recommend setting up your life (at least for these 10 weeks) to allow for working on this class work during the week (ideally daily). Don’t expect to fit it all into the weekend. Even my light weeks were at least 15 hours spent on the class (usually closer to 25 or 30).
Check Piazza religiously
If they improve anything in CS162, I hope it’s the unclear assignment requirements. They requirements were notoriously bad – assignments are written in a conversational style and it’s hard to know what is really being asked for.
Many students took to Piazza (the class forum) to question (or worse, debate) the requirements until a TA or the instructor herself came along to clarify.
Pretty much every week went like this:
- New assignment comes out – oh no, it has unclear requirements
- Someone asks for clarification on Piazza
- TA makes a call and says do it X way
- 2 days later, another student asks the same question
- Different TA makes a different call on this new thread and says do it Y way
- They have a fight, triangle wins…
- You already coded it, so do you redo it to Y or keep it as X or what?
For what it’s worth, every time this happened (and I had already coded it), I kept my code the original way and still got 100% on the assignment.
Test on Flip!
So many things happened in my code in the Flip environment that did not happen on my Macbook. Weird things, too – things that weren’t easy to spot without thorough testing. I made the mistake of not testing on Flip until I thought I was done with the assignment, only to find heaps of bugs that only occurred in that environment.
Only after the class ended did I find out about this awesome way to use Git to deploy to Flip. (I was uploading in Filezilla like a n00b.)
Use Valgrind early and often
It’s a memory management tool that’s already installed on Flip and you won’t be able to find memory leaks without it. If you wait until you are done coding your assignment, it will be harder to find the memory leak. Upload your code and check it with Valgrind every so often and you will save yourself a lot of pain.
The worst weeks were weeks 1, 2, and the final project.
Okay, they were all brutal. There were many weeks where I thought there was no way I would get everything done and I’m a workaholic. The biggest workloads were the first project (Langton’s Ant) and the final project at the end (make an adventure game).
You do actually have to contribute to the Canvas conversation topics
It’s a misguided requirement because these “conversation” threads quickly turn into 100+ people dumping commentary and links in one place. It’s not a conversation, it’s just a dogpile.
But if you contribute a few posts (I think I made 5 decent, paragraph-sized comments between January and March, evenly spaced throughout the quarter), it’s an easy 20 points that you will (probably) be very happy to have at the end.
Take every quiz twice
(Unless you get a great score the first time around, of course).
You get two attempts for each quiz. A quiz is 20 questions in 15 minutes. (I liked this format). Only the grade from the last attempt is kept. Questions are drawn from a larger pool, so you won’t get exactly the same ones the second time you take it.
My strategy was to use the first attempt to see what’s on the quiz and make my best guesses as to the answers. This gave me a feel for the questions and sometimes revealed tricky ones. I usually got about a 16/20 on my first try but Canvas tells you which ones you got wrong, and what the correct answers were, so this is a chance to see what you missed and study it some more. After a little studying I’d retake it, usually getting 18/20 or 19/20 that second time.
The final’s worth 15% of your grade, so save some steam for the end. There was a bonus, extra credit lab announced right at the last minute, too, but its points could only be applied to your lab grade.
- Weekly labs – 30% of your grade
- Quizzes – 15% of your grade
- Projects – 30% of your grade
- Group activities – 10% of your grade
- Final project – 15% of your grade
Overall impression: OSU CS162
I hated it at times, but it was worth it. I never would have pushed through some of this stuff on my own, without a grade and a degree motivating me. OSU’s online CS is meant for people with a full-time job and the occasional signs of life outside of class but I had to take a couple days off work here and there to accommodate the workload, and I barely saw my family. The most difficult parts of this class – deciphering confusing and unclear requirements – were totally unnecessary. OSU should hire a proofreader and clean up CS162’s assignments. And some weeks the workload was just pure insanity – the week with the group project stands out in particular.
But… it’s over! And I got a 97%, so I’m going to take a much-deserved week to rest up for the next class.
Onwards to CS225!
Other student reviews of CS162
Leave a comment and I’ll update this post with your review!
- Alex Learns Programming http://code.alxmjo.com/class-report-intro-to-programming-ii-cs-162/
2 thoughts on “OSU eCampus CS162 Intro to Computer Science II review & recap”
Awesome review! Thanks for writing and publishing these thoughts – it’s really helpful for those of us thinking about enrolling in OSU’s program to get an idea of what it’s like.
Great review. I’m getting ready to take 162, the final one in C++, and even after taking the summer off and studying, I’m buggin out!