Ask HN: What books should I read to improve as a software engineer?
121–127 of 127 posts
Re: Ask HN: What books should I read to improve as a software engineer?
#122It's probably useful to un-read Clean Code, though I don't really have a recommendation for a good replacement. The replacement is something like "Make a lot of mistakes and develop good taste based on your experience." If you're interested in performance, you can read https://algorithmica.org/ and https://people.freebsd.org/~lstewart/articles/cpumemory.pdf
Re: Ask HN: What books should I read to improve as a software engineer?
#123Re: Ask HN: What books should I read to improve as a software engineer?
#124I’ll have two recommendations. 1. A Philosophy of Software Design is very good. Not the whole of it but it’s short and to the point. 2. Fiction, as diverse as possible. I apologise for making assumptions but many software engineers are secretly lacking in understanding other people, what kind of of life experiences that have, how they think about the world, what is important for them. If you work with people it is go…
Re: Ask HN: What books should I read to improve as a software engineer?
#125It's probably useful to un-read Clean Code, though I don't really have a recommendation for a good replacement. The replacement is something like "Make a lot of mistakes and develop good taste based on your experience." If you're interested in performance, you can read https://algorithmica.org/ and https://people.freebsd.org/~lstewart/articles/cpumemory.pdf
algorithmica.org; only if you can read Russian, as the English version is WIP and the main version they work on is the Russian one.
Re: Ask HN: What books should I read to improve as a software engineer?
#126I have no affiliation.
Re: Ask HN: What books should I read to improve as a software engineer?
#127"A Philosophy of Software Design" by Stanford's John Ousterhout is excellent. It is quite concise (about 190 pages), but in my opinion, it includes all the essential information that the other books in that category would teach you. It leaves out a lot of cruft that over the years turned out to be non-issues (code styling, problems that come with object oriented programming, etc.) but occasionally - when the topic is…
Not Rust or TS, but i found Java to Kotlin a decent book which provides refactoring of java OOP to more functional patterns. One of the authors Nat Pryce was big into OOP design and was also a co-author of famous book Growing Object Oriented Software by Tests.