What Is OOP and Why It Exists — Procedural vs Object-Oriented

Object-oriented programming is a paradigm that organizes code around objects — bundles of state and behavior — instead of functions operating on shared data. It was created to solve a real problem: procedural code collapses at scale because any function can corrupt any global variable, and changing a data structure means finding every function that touches it.

In OOP, the object owns its state and exposes a controlled interface. You don't call withdraw(account, 500) — you call account.withdraw(500), and the account enforces its own rules like "balance can't go negative." That's encapsulation: the first pillar.

The four pillars each fix a specific procedural failure mode. Encapsulation fixes shared mutable state — data is private, only the owning object can mutate it. Abstraction fixes depending on implementation details — you program to an interface, not a concrete class, so swapping the implementation doesn't break callers. Inheritance fixes duplicated code across similar types. Polymorphism fixes type-switching code — instead of if-dog-else-if-cat, each object responds to the same message in its own way.

Java is class-based OOP — everything lives in a class. But I'd add that OOP isn't always the right tool. A CSV-to-JSON pipeline is a data transformation, and forcing it into objects adds ceremony. Java's Stream API is an acknowledgment that functional patterns belong in the language too. The senior distinction is knowing when OOP helps and when it's just ceremony.