Good videos, with context.

Make change costs visible

Software architecture videos

Software architecture videos are valuable when they help you reason about a change you actually expect to make. Begin with interfaces and dependencies, then use a worked refactoring to test whether the design vocabulary improves code.

Compare a public contract with an internal structure

Bloch focuses attention on the boundary other programmers will depend on. Metz gives you a smaller piece of conditional code whose structure can be changed. Watch them as complementary scales of design, not a prescription to introduce more layers. Before refactoring, name a likely requirement change and the existing contract that must survive it; after refactoring, count the places that change rather than the new classes.

Choose a starting point

Questions to take into the video

A clean diagram cannot establish a clean dependency structure. Avoid adopting a named architecture without checking the actual cost of deployment, testing and modification.

Explore a connected subject

Sources and selection notes

By . Updated . We compared source-video titles, available uploader descriptions and the linked archive records. The choice of starting points and viewing questions is our editorial guidance. These notes do not claim full-video viewing or independent expert review.

The complete list below preserves the October 31, 2026 snapshot and its original score order. Its labels and summaries include AI-generated source material; topic membership is broader than our selected starting points. Availability and factual claims can change. Suggest a correction.

All 177 videos in this archive topic

Browse the full snapshot after choosing your starting point.