"Technical issues can be solved, the technical problem is not the most important"
Recently, some people have solved technical problems and found a very serious problem. Their practices are the same as me start writing programs, so I will go a lot of detours. There is now a class of programmers, they always pursue "so-called technical difficulties", always put their minds on some "program code" implementation issues, write programs, to complete function, basically Do not consider any questions such as reconstruction / abstract / multiplexing, the goal is only one ---- complete the task.
The program code is to learn, but now there is too much language, can you cut a detail every language? The code is always flexible, you can't learn, you should learn from the eyes, consider something other than code, such as design mode / reconstruction abstract multiplexing / various systems design requirements analysis / database structure design / Unit test / site structure design ..., if as a single PHP programmer, it is best to find time to see something around Java, the peripheral technology of PHP is really too little.
Take the website, in fact, the structure mode of the website is really important. Good design allows you to save a lot of time, a basic enterprise promotion website, write PHP programs and modify templates (excluding page templates) As long as you can do it one day, and the structure is clear, anyone can immediately "get started" to modify your program, do you believe? Let's take an example, give you a look, then look at my statement.
I have published an article called "Create the easiest ------ PHP Development Mode" in the world, I don't know if someone has seen, our company's website "www.yeesoft.com" is used in this structure. The time completes the entire website for a week (excluding the production template) at the time.
The day before yesterday, let me take the "http://www.chinacbc.org.cn/" to make the basic function, let the customer look at it first, he sent me the structure map of the website, let me First, do the program, give me the template the next day. So I decided to use our company's website to change. However, some places are somewhat different, such as the president and vice president, everyone has a self-ending bar ......., so modified the background program first, joined several features: 1, re- The structure of the column data table is designed. 2 4. When template parsing, the function of "Multi-Column" or "Multi-Column" table is parsed completes these modifications and DEBUG for a total of 6-7 hours. Yesterday morning, the template sent it to me. I wrote a 10-line program for each template. It is called a bunch of functions, and the program is called the function interface, so as long as the parameters are paid, There will be no problem, and the time of the debugger is not used, and then modify the template, and some styles in the template are also modified. A total of 16 templates were completed 4-5 hours. Then pack it to the boss. Later, several places should be added to add functions, but there is no more than 2 minutes each time, because the function interface is very simple to be public, and the different parameter calls can be used.
The entire website has been completed in a total of 10--11 hours, and the entire structure and ideas are very clear, and SQL is also centrally managed, and anyone can understand. Instead, in the later, add the article to the article version of the version, but this is a long time, but this is the question of "website editing". That is, during the entire construction process of the website, I used to use the least amount of programmers. If you want to make a new site for the same program, it is simpler, as long as it will spend the time to modify the template.
BYW, I hope everyone supports OpenSource. You don't need you to open the entire project. You can publicize your design structure, core code, design experience, and share it together.
