Brief discussion on several details of large web site development

Intermediary transaction http://www.aliyun.com/zixun/aggregation/6858.html ">seo diagnose Taobao guest cloud host technology Hall

I have developed a number of large web sites, music portals, information portals, now the development of the Web site, are high flow of large web sites. So what I'm going to say is the teamwork in the development process and a few details that should be noted:

I. Program framework: We want to develop the site, often on the market there will be many of the same kind of open source programs, so we choose the program is not difficult, but we do not casually choose a framework, to see the program two times the development of performance, drawbacks, structural optimization, such as the suitability of several aspects. And the future development plan of the website, must take into account. So choosing a program is not a simple matter of opinion.

Second, the development process: the development of the foreground everyone knows to use designers, site layout personnel, JS engineers and so on and so on. I am here on the JS aspect, the large web site has a overall planning, so JS planning is indispensable, the following I summed up the 3 kinds of JS programming:

1, scattered type: What is the scattered type, this is my own definition, that is, when we use what effect of the time to write a piece, such benefits are convenient, easy, where to write, and do not use external file calls, for JS requirements of the site is very practical, the disadvantage is not good management, Code is often not found when modifying code.

2, Package Type: And scattered type difference is, the code is encapsulated, with file calls, encapsulation advantage is, do not conflict with other functions, make one of the package class, very practical, now most of the site is using this method. The disadvantage is that it is still not a whole class library, but it is better than the scattered management of many, it varies from person to person.

3, JS class Library: JS class library, with a lot of prototype,jquery, we take jQuery for example, now large Web sites generally use JS is nothing but two ways, one is the original JS, pure JS written site (the above two methods included), And then using the jquery framework, two ways the process is very different, but the user see the effect is the same, and some large sites are simply JS writing, without any framework, this is a technical hard standard, for different companies, this is a simple technical test, a lot of experts, JS can also write the same class library as jquery, but if you use jquery will save a lot of time, because jquery itself has a lot of plug-ins for everyone to use, completely open source. On the other hand, jquery may indeed be an app, and it's fundamentally different from the code you write. I have seen a lot of famous web sites, there are JS and jquery combined, there are simple JS, there are pure jquery, no matter how the use of the browser to see the effect is the same, the difference is that we have in the expansion, maintenance, management is different. So we write the front-end code when the use of JS to carefully consider, but also according to their ability to determine how to use JS.

Third, teamwork: good products are inseparable from the whole team, because you are not a person in the fight. In the development of technology, we must always keep communication, even a little problem, can ask colleagues to ask more, a word of things than to go to Baidu to find strong it, especially the core of the problem, planning problems, can not own unilateral to think, to together to determine whether the matter is correct, whether it can be implemented. Often rework is due to the tacit understanding of the combination of technical errors, resulting in the cost of time and leadership of the blame. Remember how you are capable and not better than the whole team effort.

Four, find bug:bug in the technical field is very hot a word, we develop the process, every moment in search of Bug,bug is also invisible. Finding a bug is sometimes even more powerful than what you've learned for days, because bugs are the easiest thing to ignore and the knowledge you learn. The release of a product can sometimes degrade visibility and authority by a bug. So before the release of the product, find bugs is the most important, but I want to say is, looking for a bug is not to be dedicated to waiting for a certain time to find, we have to work, rest, sleep when all should come to think, today I wrote what code. Will there be a problem. This time is much more than a special time to find bugs. This is the technical details, we have to use effective time to do some infinite things. It seems that this sentence is said by others. Quack.

Five, Work Summary: refers to the work summary, I subconsciously secretly said: "And TM write summary, what today?" Yes, you are the same, we sometimes make work summary as part of the job, right? What to do every day. But in fact the company is looking at your work summary is to know what you do every day, but oneself to do the work summary is to want to know oneself to learn what new knowledge, made what and yesterday different things, here also appeared a detail, is to each day oneself discovers different place summarizes, do not easily ignore, This will have a motivation for yourself, you know what? That is the invisible growth, how the ability to come, not born, is to learn by their own heart. (This section has nothing to do with technology, it's verbose.) )

The above five points, I simply summed up the hope for everyone a little useful, if there is a wrong place please blame.

I come from a gauze network (www.yeesha.com) Team Development Group, Technical Exchange Group: 37817801, the article for my original, Welcome to reprint, reprint please indicate the source.