Any laws for good software design?

Question

There's any kind of "resource" to learn good practices of software design on the most practic sense?
Like when (or not) to pass an object to a function to modify its internal state, or use it to modify some else's state.

In the sense of make good design choices that will improbe code readability, testability, mantainability, usability, clean, etc.

Things like that, for someone that knows coding, but only has being doing simple little programs for learning purposes, and wants to try build bigger programs, like a "little system" or so.
(Already familiar with SOLID)

Some sort of cheatsheet would be good.
Books also welcome.
(Reading "Clean Code" book from Uncle Bob rightnow.)

Answer 1

Martin Taylor mainly OOP and general agnostics (patterns, architecture, etc)