Clean code: why it matters, naming, functions and control flow
Clean code seen as the cost of change: Ousterhout's three symptoms of complexity, naming, small single-purpose functions, SRP/OCP class design with sealed interfaces, one level of abstraction per function, guard clauses and lower cognitive complexity.