And I don't mean the Uncle Bob style "here are some principles that most people agree on." I mean something with at least some data behind it, no matter how messy and hard to interpret. Science.
* Evidence based software engineeringg
* Empirical or experimental software engineering[^1]
Most people don't think about these things at all.
They think the rules of thumb are natural.
At present, I don't follow the latest research, but there are several famous books, which I recommend here.
- Making Software:What Really Works, and Why We Believe It
- Object-Oriented and Classical Software Engineering, 8th Edition
- Facts and Fallacies of Software Engineering
Most of the passages in those sources above are supported by detailed evidence, so following those well-marked references should lead to the latest content, except that I don't have time to do it, so I've put it aside for now.
Although this book is not a rigorous academic style, it does discuss issues related to it.
- The Problem with Software:Why Smart Engineers Write Bad
It should help you.
[^1]:https://stackoverflow.com/questions/1835059/what-is-evidence...