Programming is also a matter of planning

        Looking for information, I suddenly found something from two years ago, which was in May 2010. At that time, I was very keen on technology, and worked overtime every day. In addition to completing the company's tasks, I made some other things myself and researched new ones. At that time, I wanted to make a custom framework by myself, completely throw away those third-party good frameworks, and assemble them all by myself. After a few months of overtime, I finally got a simple version. . Then I found a code generation tool, which was also written by me, but it will play a great role in the project later. I remember that the company received a medium-sized SCM order, and it was stipulated that it would take 3 months to complete, but when we actually code In just one month, 2 coders can not prove the completeness of the requirements in the middle, and we use this code generation tool to save a lot of time and cost.

         What I said above is all bullshit. In fact, these two products are almost half-finished products, because there are still many imperfections. Later, I have been shelving them without maintenance, so they are regarded as failed works. The data also recorded the logs I developed at that time, that is, some problems I encountered, work plans, functional fixes, and technical difficulties. Hey, it is difficult for these fragmentary things to become a big climate.

        Now I keep thinking, why is it like this? I recalled the situation when I was developing at that time. Many things were what I thought of doing, improvisation, random, and there may be many functions in the middle that were well implemented and useful. I'm also excited about the technologies that are used, but the functionality that is implemented is missing an empty shelf. There has always been either a direction or a time limit. There is no general outline.

 

          Now I want to summarize it as follows, to find the direction for future products, and don't repeat the same mistakes.

 

  •  No matter what product, software, website, or even a tool you make, you must have a general plan and a clear execution time. You can only do one thing best in a time period. Within a period of time, according to your own Actual ability and conditions allow, don't set the goal too big, only move forward step by step.
  •  Don't do whatever comes to your mind, do something practical and useful, and don't do something empty because of technology or personal interests.
  •  Persistence in doing things, don't give up halfway, persistence is victory, keep conquering yourself, keep learning.
  •   To do something useful, choose the most important and optimal function from the list of many functions.

 

         ps: I hereby keep that in mind, to spur myself not to make the same mistake. Keep learning, keep summarizing.

  

       

Guess you like

Origin http://10.200.1.11:23101/article/api/json?id=327014632&siteId=291194637