Skip to main content
Penn State
Computer Science
3 credits

Penn State CMPSC 132: Programming and Computation II: Data Structures

CMPSC 132 continues from 131 with data structures and algorithms in Python: linked lists, stacks, queues, trees, hashing, recursion, and runtime analysis. It's the course Penn State CS students most often name as the major's first real filter.

Fennie is independent and not affiliated with Penn State University. This is an unofficial study guide.

What makes it hard

Recursion and linked structures are the famous walls: you have to reason about references and call stacks abstractly, and trial-and-error coding stops working. Assignments get long, exams test implementing and tracing structures by hand, and the curve reflects a class where the gap between understanding and pattern-copying gets fully exposed.

What you'll cover

  • Object-oriented programming in depth
  • Recursion
  • Linked lists, stacks, and queues
  • Trees and binary search trees
  • Hashing
  • Big-O and runtime analysis

The CMPSC 132 study guide

How to study for Penn State CMPSC 132, step by step.

  1. 1

    Enter with CMPSC 131 actually solid

    Functions, classes, and basic recursion are assumed fluently from day one. If any of them are shaky, rehab them in the first week. CMPSC 132 will not slow down for review.

  2. 2

    Draw every linked-structure operation

    For each insert, delete, and traversal, diagram what every reference points to before and after. Visual tracing is the skill the course actually builds, and exams test it by hand.

  3. 3

    Learn to think inductively about recursion

    Trust the recursive call to handle the smaller case while you reason about one frame. Students who trace every call of every example burn out; the inductive mental model is the breakthrough.

  4. 4

    Start assignments the day of release

    The assignments get long, and debugging linked structures and recursion takes calendar days, not heroic nights. The curve fully exposes the gap between early starters and deadline coders.

  5. 5

    Attach Big-O to everything you write

    Note the runtime of each method as you implement it and be ready to justify it. Runtime analysis questions are reliable exam material and pure points for students who made it a habit.

Today

Today's CMPSC 132 plan

Preview
65 min

What a Fennie Daily Plan looks like for CMPSC 132. Yours is built from your own syllabus and adapts every day to your deadlines and progress.

0 / 4 done~65m remaining
Keep this plan free

First plan free, no card required. Fennie is independent and unaffiliated with your school.

FAQ

Is CMPSC 132 at Penn State hard?

It's widely called the first real filter of the CS major. Recursion, linked structures, and runtime analysis demand abstract reasoning that brute-force coding can't fake, and exams test hand-implementation. Students who start assignments early and practice tracing consistently get through.

How do I prepare for CMPSC 132?

Enter with CMPSC 131 material genuinely solid, especially functions, classes, and basic recursion. During the course, draw diagrams for every linked-structure operation and trace recursive calls on paper; visual tracing is the skill the course actually builds.

Why is recursion so hard in CMPSC 132?

Because it requires trusting the function to solve the smaller case while you reason about one frame, a mental model, not a syntax pattern. Students who try to trace every call of every example burn out; learning to think inductively is the breakthrough.

More Penn State courses