OOP Principles

OOP Principles

The video demonstrates inheritance, method overriding, polymorphism, and encapsulation through a small refactor of a Java command-line formatter and a review of a movie class.

Inheritance and Method Overriding

Jan shows how to add an alternate “hype” formatter that changes how command-line messages appear.

• The standard CLIFormatter is used by default.
• HypeFormatter extends a formatter class and overrides formatting behavior. For example, success messages can appear in bold, green, and uppercase, while errors can use red styling.
• The program checks its startup arguments. If it is run with --hype, it selects the hype formatter; otherwise, it keeps the standard formatter.
• The formatter is switched through an active formatter reference and a setter method.

During implementation, Jan adjusts the design: instead of overriding the existing message-printing methods, the code uses separate methods for formatting success, error, and informational messages. Jan also emphasizes reviewing AI-generated code: an early issue resulted from a mismatch between methods that returned strings and methods declared as void.

Polymorphism and an Abstract Formatter

Gabe explains how polymorphism relates to inheritance: different classes can provide different behavior for the same method.

• Both formatters share methods for formatting success, error, and informational messages.
• To make the design more reusable, the code is refactored to introduce an abstract Formatter class.
• The abstract class declares shared methods, while concrete formatter classes implement them in their own ways.
• Both the standard and hype formatters inherit from the abstract class rather than having the hype formatter inherit directly from the standard formatter.
• Code can hold a reference to the common formatter type and select a specific formatter at runtime. When a formatting method is called, the selected object’s implementation is used.

Gabe says this reduces duplicated code and makes the formatters easier to extend, troubleshoot, and update. He compares the shared formatter reference to a remote that can control different TVs: changing the active formatter is like switching which TV the remote controls.

Encapsulation

Gabe uses the movie class to illustrate encapsulation.

• Movie fields such as title, director, genre, year, and movie ID are private, so other classes cannot change them directly.
• A constructor is used to create movie objects.
• The example does not use getters and setters to update movie data; changes are handled through SQL and the database.
• More broadly, encapsulation means keeping data and related behavior appropriately contained and exposing access only through intended mechanisms. This helps prevent unintended changes and reduce errors.

Speakers and Sources Featured

• Jan — Demonstrates inheritance, overriding, and selecting a formatter through command-line arguments.
• Gabe — Explains polymorphism and encapsulation.
• GitHub Copilot — Shown as a coding assistant used during the refactor; the presenters advise reviewing its suggestions.
• Dr. B — Mentioned as someone students can contact, but does not speak in the video.