After reading The Way to the Top
As a beginning computer language student, there are always various problems that plague me during the language learning process. Before I read "The Way to Simplicity", which is a classic software engineering book, I used to go for complexity and tedious code design. Because I thought it reflected my personal level, more "advanced" or something like that, I would keep adding new code and logic to realize a certain function, which made the whole code hard to understand and maintain. I've also seen people use a lot of nesting and complex logic in their code, which makes subsequent changes and maintenance very difficult.
However, after reading The Great Tao of Simplicity, I realized that this is only a "layman's" view of computers, but not in the eyes of those of us who actually learn, understand, and use computer languages. Complex logic and lots of nesting should not be the essence of computers. On the contrary, I think the essence of the computer should return to the 0 and 1 so simple and clear. Just like Yugong in "The Way is Simple", only a simple digging is needed to make the program run. After that, the cycle is completed with "endless generations".
Secondly, on the basis of "endless children and grandchildren", we should think about "accumulating salary and burning it", which is the further step of "method". And the emergence of the method is also to make the process more concise, as the title of the chapter in the text 'is the lazy man made the method' is to make the 'lazy man' in the process of programming more convenient, more concise, more 'without thinking' to write the desired The goal is to make the programming process easier and more concise for the 'lazy' person, so that they can write the program they want 'without thinking about it'.
Combining the above two points, I realized that the past practice would lead to a decrease in code quality and team efficiency. Complex code increases the difficulty of bug generation and troubleshooting, while simple design can help the team better collaborate and deliver high-quality products. Only with simplicity and clarity can we be more friendly to ourselves and others, and achieve the goal of "good for you, good for me, and good for everyone".
To avoid falling into the trap again, I plan to change the way I design my code. I will focus on simplicity and clarity of code, avoiding unnecessary complexity and nesting. At the same time, I will study and learn from some design principles and practices presented in the book, such as the single responsibility principle, the open-close principle, and other such things, to guide myself to better design and write code.
As for the text of the team management, communication, communication, due to my skills are still shallow, have not eaten the dividends, and did not eat any losses, so the understanding of this aspect of the delivery of shallow. But through my life all kinds of things, but also can be empathy, flow in the form of communication, will indeed cause a lot of trouble, such as between the party and the programmer, as shown in the figure below:
It would be easy to make a mockery of such a situation.
Finally, I summarize my views and opinions as follows: I think computer language is just a tool for programming, just convenient or not in different situations. The so-called simplicity, not language simplicity, but thinking simplicity, thinking straight to the point, to the point. Only in this way can we really touch the threshold of simplicity, understand simplicity, and maximize the effect of simplicity.
This allows you to hit the nail on the head and get right to the point, whether it's in your programming language, in communicating with people, in managing your team, or even in the depth and breadth of your thinking.
Of course, through continuous learning and practice, I believe I can improve my software engineering skills and better avoid the mistakes I often made in the past. In my future work, I hope to be able to improve the efficiency of my team and the quality of my products through concise code design.