1. The harvest of the code The
first time I did a payment project, the merchant module development did not have a framework that could run at the beginning, and there were no conventions. It was particularly uncomfortable to change it by various means. The most regrettable thing is that I didn’t think about the business carefully and then did the development. I was particularly impressed. When a project starts, the business must be familiar. When the business is blurred, it is irresponsible and just Blind, you need to go into the interface process in detail before you can enter the development. During the business development process, doubts must be raised. Product managers are not a panacea, and there is no mistake. When there is ambiguity about the business written by yourself, unless someone convinces By yourself, everyone will come out to discuss and remember the four words brainstorming.
2. Gains
from the development process Talk about the specific development process. You must be clear about every interface you have. When writing code, you must have specifications. It is scary to have no specifications. When the project gets bigger, sometimes the code you write is not Now that I know, I have this feeling that my code is even more annoying when others see it. Don't bury such pits and waste other people's time and your own time. The standard is a kind of agreement for efficient development, and I have realized it, and I must follow the standard in the future. The development of the front-end and the back-end is separated, which can be regarded as low coupling in work efficiency. The back-end dao layer, business layer, and controller layer also have to be low-coupling. I made a mistake last time. I query an object and directly return the defined unified object in the business layer. Imagine if someone else wants to be in the business just to get One of my objects, is it necessary to analyze my subpackaged objects? It is an irresponsible way of writing. I am very impressed. I will remind myself every time I write. For useless data, never return it to the caller who called you. Don't just write almost the same code just because the project is small, take each project seriously and treat it as a large business volume. It is also interesting to return the objects to the front-end in a unified way. The purpose is to let the front-end understand the status and data of the things that our back-end gives them, and how to express them easily. This is a modification to realize.
3. Gains from learning methods
First of all, we must learn to bow our heads, see the strengths of others, and see our shortcomings better, so that we will have the sincerity to learn from others. Walking with a wise man, you should feel fortunate. Don't talk about the environment. It depends on your own behavior. There are things you can learn in every environment. The key depends on what you think and how you look. There is always something you can earn. When we don’t have strong skills and no goals, we should first keep ourselves busy. Sometimes what others say is that it’s all other people’s experience. How can we understand other people’s ways? Get busy yourself, do more, and meet later. More problems, more problems solved, this is the fastest growth. To dispel the thought that you once wanted to reach the sky in one step, the premise of doing fast is to be careful and practical. Do things first, and then do more. If there are more, there will be a coincidence. I have realized it.
我的分享就到这里，一个做了十几年的大佬，我知道他经常忙到12点，我还迷茫啥，那么优秀的同行人和资源，没有理由不跑起来。时间长了，每隔一段时间回头看一下自己，每天每个月每年，都去总结一下，有时候回头看一下，是为了向前走，谢谢看到我文章的人，感谢帮助我的人，对自己有责任，对团队有责任人，对帮助我的人更要感谢！！！