Skip to main content
UW-Madison
Computer Sciences
3 credits

UW-Madison CS 300: Programming II

CS 300 (officially COMP SCI 300) is UW-Madison's object-oriented programming course in Java, covering classes, inheritance, interfaces, exceptions, recursion, and intro data structures like array lists and linked lists. It's one of the largest courses on campus, since it gates the CS major and serves data science, engineering, and statistics students besides.

Fennie is independent and not affiliated with University of Wisconsin-Madison. This is an unofficial study guide.

What makes it hard

The jump from writing procedures to designing classes is the real shift: inheritance, polymorphism, and reference semantics demand a mental model of objects in memory that CS 200 never required. The pace is brisk because it's a gateway, exams test writing and tracing object-oriented code by hand, and recursion arrives as the unit that separates the room.

What you'll cover

  • Classes, objects, and encapsulation
  • Inheritance and polymorphism
  • Interfaces and abstract classes
  • Exceptions and I/O
  • Recursion
  • Array lists and linked lists

The CS 300 study guide

How to study for UW-Madison CS 300, step by step.

  1. 1

    Build the objects-in-memory mental model early

    Draw what references point to for every example: which variable holds which object, what changes when you assign. Reference semantics power half the exam's tricky questions, and the diagram habit is how the model forms.

  2. 2

    Write small class hierarchies from scratch

    Inheritance and interfaces only click when you design with them. Weekly from-scratch exercises (a base class, two subclasses, an interface) beat rereading lecture examples by a wide margin.

  3. 3

    Give recursion patient, spaced practice

    It's the unit that splits the room. Learn to trust the recursive call inductively rather than tracing every frame, and practice across structures (numbers, strings, lists) over multiple weeks.

  4. 4

    Hand-write code under exam conditions before each test

    CS 300 exams demand producing and tracing Java on paper. Simulate it: a blank page, a problem, no IDE. The gap between editor fluency and paper fluency is where grades drop.

Today

Today's CS 300 plan

Preview
65 min

What a Fennie Daily Plan looks like for CS 300. 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 CS 300 at UW-Madison hard?

It's the CS major's gateway and grades like one: brisk pace, object-oriented design, and recursion, with exams requiring hand-written Java. Students who practice writing class hierarchies and recursion steadily handle it; students who pattern-match assignments meet a wall at exam time.

Can I take CS 300 without CS 200?

Yes, with prior programming background. Many students enter via AP credit or self-taught experience and satisfy the prerequisite through placement. You need real comfort with loops, methods, and arrays in some language; the course rebuilds syntax but not programming fundamentals.

What grade do I need in CS 300 for the CS major?

Requirements have shifted over the years, so check the current declaration criteria with CS advising. Practically: CS 400 and everything after assume 300's material completely, so aim for mastery regardless of the threshold.

More UW-Madison courses