OOP and Software Engineering

encapsulation

hiding internal state behind interface

abstraction

simplifying complex details through model

inheritance

derive class from another class

polymorphism

one interface with multiple implementations

composition

building object from other objects

interface

contract of methods without implementation

abstract class

class not meant to be instantiated directly

coupling

degree modules depend on each other

cohesion

degree module responsibilities belong together

DRY

do not repeat yourself

YAGNI

you are not gonna need it

SOLID

principles for object oriented design

single responsibility

class should have one reason to change

dependency injection

provide dependencies from outside object

unit test

isolated test of small behavior

mock object

fake dependency used in tests

refactoring

change code structure without changing behavior

technical debt

short term choices that increase future cost

code review

peer review of code before merge

version control

system for tracking code changes