Why it matters: I liked this book. It went over the common areas that a software engineer needs to deal with. Short, scannable chapters and a good overview made this to an enjoyable read.
#Things to consider
- Changing large existing codebases is a skill refined over years—decades, even.
- Protect your system by programming defensively with safe and resilient coding practices.
- Healthy teams use practices such as project retrospectives to discover inadvertent debt and discuss when and whether to pay it down.
- To keep configuration changes safe, configuration should be version controlled, reviewed, tested, built, and published.
- Spend a portion of each week reading. There are many different sources: team documentation, design documents, code, ticket backlogs, books, papers, and technical sites.