I found Richard P. Gabriel whilst researching the concept of "habitable code", which seems to fit my intuition about what makes for good code.
A codebase should be views as Living Structure not as a exercise in High Modernism.
This line from the intro in the book struck me as the way I've seen people use the GoF book incorrectly:"..the ideas of A Pattern Language cannot
be applied mechanically. Instead, these ideas—patterns—are hardly more than
glimpses of a much deeper level of structure, and is ultimately within this deeper
level of structure, that the origin of life occurs"
But as I understand her she argues that the real 10x lies in taking a broader perspective and thinking about the people and the "aliveness" of the code in an Alexander way.
Which then leads to a 10x not in the time to market but in some other metric, maybe 10x less entropy, or big hary messes in the long run.
Some examples are the functional map/reduce/filter/etc patterns. Turned 10+ lines of boilerplate code into one line.
Or look at how the patterns that Sinatra introduced about building web frameworks spread incredibly quickly to almost every other language.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!