Skip to main content
UGA
Computer Science
4 credits

UGA CSCI 1302: Software Development

CSCI 1302 is UGA's second programming course and its real gatekeeper — object-oriented Java (inheritance, polymorphism, interfaces, generics) plus the professional toolchain: the Unix command line on the department's Odin server, Git, unit testing, and strict style checking. It's required for the CS major and the prerequisite for nearly everything after.

Fennie is independent and not affiliated with University of Georgia. This is an unofficial study guide.

Build my CSCI 1302 study plan

What makes it hard

The difficulty is the environment as much as the material: students used to clicking a run button suddenly compile from a terminal over SSH, manage deadlines that don't move, and lose points to style violations a checker catches automatically. The projects are substantially bigger than 1301's, and starting one the weekend it's due is the classic way to fail.

What you'll cover

  • Object-oriented design: inheritance and polymorphism
  • Interfaces and generics
  • Unix command line and SSH workflow
  • Git and version control
  • Unit testing and code style
  • Exceptions and I/O

The CSCI 1302 study guide

How to study for UGA CSCI 1302, step by step.

  1. 1

    Get fluent on the command line in week one

    CSCI 1302 runs through a terminal on the Odin server, and fumbling with cd and vim while a project clock ticks is self-inflicted pain. Drill the basic workflow until it's boring before the first project lands.

  2. 2

    Start every project the day it's assigned

    1302 projects are sized so a weekend isn't enough. Reading the spec and writing a skeleton on day one surfaces the hard parts while there's still time to ask about them.

  3. 3

    Draw the class hierarchy before writing it

    Inheritance and interface questions dominate the exams. Sketch which class extends what and which methods get overridden — on paper — before and after each project.

  4. 4

    Commit early, commit often

    Git is graded and Git is your safety net. Small frequent commits mean a broken refactor costs minutes, not the night before the deadline.

  5. 5

    Let Fennie hold the deadlines

    Upload the CSCI 1302 syllabus and project specs and Fennie's Daily Plan backward-schedules each project into daily working sessions, with OOP-concept quizzes generated from your actual materials before exams. Free to start.

    Start my CSCI 1302 plan free

How Fennie helps with CSCI 1302

Fennie's Daily Plans backward-schedule CSCI 1302's big projects into daily working sessions, because the course's deadlines are famously unforgiving and the projects can't be weekend jobs. Use chat to reason through inheritance hierarchies and decode cryptic toolchain errors, and quiz yourself on the OOP concepts the exams target.

FAQ

Is CSCI 1302 the weed-out course at UGA?

It plays that role for the CS major — not because the Java is exotic, but because it adds the professional toolchain (terminal, Git, testing, style checks) and project sizes that punish procrastination. Students who start projects early and learn the tools deliberately get through fine.

What is the Odin server in CSCI 1302?

Odin is the UGA Computer Science department's Unix server where 1302 work is done over SSH — you compile, test, and submit from the command line. Getting comfortable in that environment during the first week is the single highest-leverage thing you can do in the course.

How do I prepare for CSCI 1302 before the semester?

Make sure your 1301 Java is genuinely solid — methods, arrays, and basic classes without looking things up — and spend a few hours learning basic Unix commands and Git. Students who arrive with those two foundations spend the semester on the actual material instead of the tooling.

Pass CSCI 1302 with a plan, not a cram

Upload your CSCI 1302 materials and Fennie generates a Daily Plan paced to your deadline — plus chat, flashcards, and quizzes built from the actual course content.

Get started free

More UGA courses