I'm a new college grad. I find my code still isn't very clean and I don't have a good answer to design decisions and abstraction decisions. What is a good book to make me a better programmer who can understand and write more complex codebases?
NASA’s 10 rules for writing mission-critical code:
1.Restrict all code to very simple control flow constructs.<p><pre><code> ----Gerard J. Holzmann, NASA JPL lead scientist.
</code></pre>
Clojure Aphorism: A tangled web of mutation means any change to your code potentially occurs in the large.<p><pre><code> ---- The Joy of Clojure (2nd Edition, Chapter 10)
</code></pre>
Bad programmers worry about the code. Good programmers worry about data structures and their relationships.<p><pre><code> ---- Linus Torvalds
</code></pre>
Metaphors for a Richer Understanding of Software Development.<p><pre><code> ---- The most valuable chapter of "Code Complete" : Chapter 2
</code></pre>
Principles-based are better than rules-based.<p><pre><code> ----International Accounting Standards
</code></pre>
My Pure Function Pipeline Data Flow
<a href="https://github.com/linpengcheng/PurefunctionPipelineDataflow" rel="nofollow">https://github.com/linpengcheng/PurefunctionPipelineDataflow</a>