


- BOOK COLLECTOR SOFTWARE REVIEW HOW TO
- BOOK COLLECTOR SOFTWARE REVIEW CODE
- BOOK COLLECTOR SOFTWARE REVIEW PROFESSIONAL
Before this book I used to think that Javascript is "bad" or a "hacky" language. Javascript: The Good Partsby Douglas Crockford.I found the parts on how C# implemented generics under the hood and the sections on covariance and contravariance especially memorable. It made me realize how many things I did not know. Just when I thought myself of being an expert - knowing all that is to know on memory allocation, garbage collection, LINQ - I read this book. C# is the language I probably understood down to the nitty-gritty details. but where to start? This book gives practical suggestions And to refactor safely, we'd need to have tests first.
BOOK COLLECTOR SOFTWARE REVIEW CODE
Touching it this sphaghetti code somewhere breaks the system. Legacy code has no test and is not written to be testable. Working Effectively with Legacy Codeby Michael Feathers.It covers the different large scale concepts - both those that I've gone through in this post on distributed systems - together with real-world examples. The most practical book I've found so far on distributed systems. Designing Data-Intensive Applicationsby Martin Kleppmann.It changed how I approached code readability, testing, and maintenance.
BOOK COLLECTOR SOFTWARE REVIEW PROFESSIONAL
I read this book after having about five years' professional coding experience. A reference book of coding best practices/patterns for a healthy codebase with some case studies. There are few books like this, that discuss software design in a simple and approachable way, while leaving the reader novel and practical concepts to use.
BOOK COLLECTOR SOFTWARE REVIEW HOW TO
I wrote a longer article with advice on how to prepare for the systems design and coding interviews.The author, Gayle, trains large and small tech companies on how to do coding interviews well: she did this at Uber, where we made changes following her help. Cracking the Coding Interviewby Gayle Laakmann McDowell is a classic to prepare for the data structures and algorithms interviews.A great intro, or refresher for all the algorithms that you'd likely need to use at a tech company. This book from Alex Xu is the most promising one as of yet. System Design Interview - An insider's guide by Alex Xu: I've so far not seen good book resources to prepare for the systems design / architecture interview.The book comes with 1, 2 and 4-week learning plans as well. She wrote the book after she found Cracking the Coding Interview to be too Java/backend-focused. A fresh take on navigating the tech the interview process, tailored for frontend engineers.


Note that none of the below links are affiliate links or sponsored. See also my list of 100 tech book recommendations for software engineers, EMs and PMs. This is a collection of software engineering and engineering management books that I have read and would recommend to others.
