I used to write code, which is simple and crude. The implementation is good, regardless of the language, framework, and mode. However, when I write too much, I often start to reduce the server burden for the optimization of a website with less than 100 daily traffic. For a module that cannot find a good way to decouple, I will overwrite the entire project; constantly trying to find an optimal solution in different open-source frameworks; failing to follow the official recommendations of languages and frameworks to implement functions is always awkward. In short, if you don't write the code that feels perfect, you don't want to write the project any more. Instead, you just want to find the language, framework, and pattern that can be more perfect. How can this problem be solved? I used to write code, which is simple and crude. The implementation is good, regardless of the language, framework, and mode.
However, when I write too much, I often start to reduce the server burden for the optimization of a website with less than 100 daily traffic. For a module that cannot find a good way to decouple, I will overwrite the entire project; constantly trying to find an optimal solution in different open-source frameworks; failing to follow the official recommendations of languages and frameworks to implement functions is always awkward.
In short, if you don't write the code that feels perfect, you don't want to write the project any more. Instead, you just want to find the language, framework, and pattern that can be more perfect. How can this problem be solved? Reply: It's okay. It will be corrected if you fail to deduct the salary several times and lose the job. Rough, fast, and fierce are also aesthetic! You need to know that maintaining the low entropy that you do not need will make your efforts better than the benefits you get. This is an imperfection in itself.
Write the code that meets your current level. In this case, I want to know how the project manager came live. :)
But which of the following is NOT a perfectionist who has taste? However, in a limited period of time, it is of course the first priority to complete the development task. If there is time remaining, review, improve, and improve. Or, the problem reported later points to poor code quality or readability. The sooner refactoring is done, the better. Looking for a girlfriend doesn't mean to think about these things. It cannot be a good thing, but it cannot be a bad thing. At least it means that you have a pursuit and love to write code. This is the driving force behind progress. I have been working for more than four years, and my colleagues are always confused about writing code. I like to delay. It's too slow for my freshman year. I need to wipe my ass every time. Later, I simply wrote the code without being too slow, and deliberately kept a small bug. This is far away. I just want to say that it is a torment to work with people who do not love writing code. The pursuit of perfection is too much, so it is not necessary to have any flaws:
- The development speed will be slowed down during the rush, and may be criticized.
- In the new product R & D stage, the product manager may say this function is not needed at any time ......
When you work overtime to write code and modules that you think are almost perfect, people will be abandoned in a single sentence, or the demand will not apply as soon as it changes, which will greatly affect your enthusiasm and mood, it is not good to resign because of this anger. In fact, there is no perfect code, a perfect architecture, and the application scenario is nothing more than a shit. Balance and trade-offs must be learned. In the case of cost, resource, time constraints, and leadership changes, the product, architecture, and code writing are the same. I can only worry about things that have nothing to do with technology. I am so tired of using TDD to write code. No matter how you optimize it, you must first pass the test.
If UT is not enough, write the IT and ST code first.
So your focus will change to another one. Try it. Write C, you will be unable to find the optimal solution. Isn't that a good thing?
