Sublime
An inspiration engine for ideas
When I’ve read other descriptions of software design, I’ve found them to be missing the critical elements of “how much?” and “when?”
Kent Beck • Tidy First?
The Gang of Four stated two principles of good object-oriented design that were present in all the patterns: “favor object composition over class inheritance” and “program to an interface, not an implementation.”8
Adam Barr • The Problem With Software: Why Smart Engineers Write Bad Code (The MIT Press)

I'm very big on radically simplifying products by removing features that don't carry their own weight.
Marty Cagan • INSPIRED: How to Create Tech Products Customers Love (Silicon Valley Product Group)
Because we are in the fairytale land of the perfect development process, we might as well employ separate developers: one who writes features and one who enables them to be broken.
Jason Arbon • How Google Tests Software
Modularity is an indispensable foundation for Conway’s Law as well. That’s because modules are where we should capture critical communication and what is learned from it. At the same time, modules can save teams from smearing mud all over their solution space. Modules are used both as conceptual boundaries and as physical compartments.
Tomasz Jaskula • Strategic Monoliths and Microservices: Driving Innovation Using Purposeful Architecture (Addison-Wesley Signature Series (Vernon))
if you use the principle of orthogonality, combined closely with the DRY principle, you'll find that the systems you develop are more flexible, more understandable, and easier to debug, test, and maintain.
David Thomas • The Pragmatic Programmer: From Journeyman to Master
Our purpose, in the end, is to achieve more with less code. We aspire to raise ourselves from programming in terms of control flow and data manipulation, to composing programs from smaller programs—where objects form the smallest unit of behavior.