This article argues that effective software design requires a deep understanding of the specific codebase, which generic design advice often lacks. It highlights the importance of concrete discussions among engineers familiar with the system, while acknowledging that generic principles can still guide new projects or help in decision-making. The author critiques the role of software architects who provide high-level designs without real accountability for implementation.