Skip to content

Unit 1 Overview

By the End of Unit 1, You Will Be Able To...

  • Set up a professional Java development environment and run your programs from the command line.
  • Build and run Java applications using Ant, the same kind of build tool used in real-world Java projects.
  • Save, version, and share your code using Git and GitHub.
  • Read data from text files and write results back to files in your Java programs.
  • Use Lists and Sets to store, organize, and work with collections of data.
  • Write Javadoc comments so your code is clear, consistent, and professionally documented.
  • Design and build a multi-class Java application from a written specification.

You may not know how to do all of these things yet. That is completely fine. This unit is designed to take you from where you are now to where you need to be, one step at a time.

Learning Objectives

By the end of this unit you will be able to:

  1. Compile and run Java applications using Ant and shell scripts.
  2. Use git add, git commit, git push, and git tag from the terminal.
  3. Create and manage issues in GitHub.
  4. Read files line-by-line using Java I/O classes (BufferedReader, FileReader).
  5. Write to files using Java I/O classes (PrintWriter, FileWriter).
  6. Use List and Set from the Java Collections Library.
  7. Document all classes and public methods with Javadoc comments.

Using AI in This Unit

AI is a tool, not a shortcut

In this unit you'll encounter patterns — file I/O, git commands, Javadoc — that AI tools can generate instantly. That's fine for exploration, but labs and assessments require you to write and explain this code yourself.

Practical ways to use AI well in Unit 1:

  • Git commit messages: Ask AI to draft one, then evaluate whether it's specific enough. A vague AI message is worse than a short human one.
  • Understanding error messages: Paste a compile error and ask what it means — great for learning.
  • Concept review: Ask AI to quiz you on topics from the What You Should Know page.
  • Javadoc first drafts: AI can generate tags, but AI Javadoc often just restates parameter names. Always revise to describe what your method actually does.

If AI generates code you don't understand, don't submit it. Ask for help; understanding the code is the point.

Tips for Success

  • Commit early and often. Don't wait until a something is "done." Small commits with clear messages are much easier to debug.
  • Run git status constantly. It's the fastest way to stay oriented.
  • Fix Javadoc warnings before submitting. Run ant jdoc and fix every warning.
  • Read the error message before asking for help. It usually tells you the file, line, and problem.
  • Online students: The videos page has recordings for each topic. Watch before the corresponding lab, not after.