Like @JohnFen said, my style has also evolved over multiple decades and it's hard to pin it down to one (or even a few) specific titles. But I suppose <i>Teach Yourself C</i> by Herbert Schildt deserves a nod, as it's basically the book I first learnt programming from.<p>Other than that, I can recall being influenced by a number of the <i>X: How To Program</i>[1] books by Deitel and Deitel. I might also mention <i>Rapid Development</i> and <i>Code Complete</i> by Steve McConnell. And <i>The Pragmatic Programmer</i> had some influence.<p>[1]: including "C: How to Program", "C++: How to Program" and "Java: How to Program".
My coding style has evolved over the decades and I can't honestly say that any book had a major influence over what it is today.<p>But, early in my career, the book that was most influential to my style was the K&R, mostly because it corrected bad style habits I had learned from languages before I learned C.
<a href="https://linux.die.net/man/1/indent" rel="nofollow">https://linux.die.net/man/1/indent</a><p>I remember reading through it and deciding options based on what I’ve seen elsewhere. Later I just wrote in the chosen style without re-indent(1)ing whole files, cause this is generally a bad idea in my book.<p>The only change I made in around last ten years was using “}\nelse {“ because I realized that I’m post-newlining the preceding block anyway for visibility and “\n\n} else {“ looks kinda ugly.
Designing Data-Intensive Applications, Martin Kleppmann (O'Reilly 2017)<p>The Pragmatic Programmer, Andrew Hunt, David Thomas (1999)<p>Gwynne's Latin, N. M. Gwynne (2015)
After reading Uncle Bob's bible many years ago, I thought about it as <i>the</i> sacred script, and tried to follow it to the t. During the next couple of years I learned that many of its advises need to be taken with a varying amount of salt - though I think that book can be still recognized in most of my work, if at least in parts.