Through out this book the author Gary McLean Hall tries to explain how to make code or software in general more adaptive, so it could be shifted easily once a new requirement comes, a change in dependencies or any other valid reason.

In the beginning Gary goes through how a project is managed, roles are spread and sprints planning.

Explaining each role responsibilities in details and the hierarchy of decisions.

While trying to back it off with examples and made up meetings seniors, it would be fair to say that it delivers the wanted point.

After that, he goes through many scenarios into why writing adaptive code is a key concern for software lifecycle.

Explaining the concept of extension points to help shift any technology or requirement change as smooth as possible.

Following with that comes our famous S.O.L.I.D principles with each holding its own chapter showcasing:

• When was it first mentioned.
• The idea on why was it set as a principle.
• How to use it in a proper way.
• What benefits dose that give on our overall structure.
• Code examples on how to use it.

At the end we go to see how a software team handles the hole deal.

From project manager getting the requirement to sprint meetings with a fun dialog of discussions along the way showing how the team is thinking and working.

I found the dialog is one of the most interesting parts of the book, because it connected many parts to a real world senior, were you could create some technical debt and how to handle changes and many more!.

I think the book is aimed to a more beginner yet intermediate level developers but would defiantly recommend for any level as it holds many small interesting tricks and tech.

I would leave you with this great graph (The Hyper Cycle)

Such a great graph were it shows how the expectations for any new tech is peaked after the trigger (first encounter).

Then how it falls from all positive to get us in a disillusion state, but there is where it should be fine tuned to meet our needs.

Book link: Microsoft store