Although this book has been around for some years, I still think it is necessary to be read, especially for a low-level programmer like me.
It is mentioned in the book chapter 5 reconstruction:
Every software or module is designed to have its three responsibilities
First, the work done by it running is the most basic.
Second, adapt to changes. Things are constantly evolving and changing, so software modules must also grow and progress amidst changes. Time passes by one minute and one second. We may have one more cell in this second than the last one. Only by embracing change can we have tenacious vitality. . So let us not resist change. Don't continue to resist, at least from now on.
Third, communicate with the people who read it. Both good and bad machines will execute the code, and the results of the execution may be the same, but the mood of the people watching it is very different for different codes. Maybe the code you write is still your own the most. Maybe you cheated a teammate or a team. Remember that the code is written for humans to see, the machine does not understand your thoughts, only knows to execute, and humans can read you. Code is the second language we communicate with others.