I think the general part of the website is

I think the general part of the website is

This image was edited by xmind. You are welcome to correct or add it!

Let's talk about my understanding and problems with website development.

I think the front-end of a website is very important:

1. Elegant text tips

2. Reasonable page design

3. Appropriate script Effects

As soon as you enter this website, you will feel very comfortable. In addition, there are eye-catching special effects on the basis of comfort, and there are more intimate tips, I believe it will certainly give visitors a unique impression, let them remember this website ., Even if they do not get the information they want.

CSS

With CSS3's strong attack, the next page effect will depend on CSS3. Although browsers that do not support CSS3 will remain for a while, it will be the next trend to support CSS3. So now we have to gradually enhance our website, and add CSS3 to our website, so that our viewers can see it and give them a sense of height. Currently, a very fashionable technology is called responsive websites. It is a good method to show different styles and increase the experience according to different widths, but I personally feel that it is quite costly to implement multiple sets of CSS based on media queries. OOCSS is a term I heard a few days ago. Now I am using this method to extract the common part, but in this way, I think it is very difficult to implement responsive websites. Learning CSS3 will be helpful for the development of B/S architecture in the future. The result is collected from the StatCounter Global Stats website. The first one is the result of 2013, and the second one is the result of January to July 2014, we can see that the markets for browsers that do not support CSS3 are being eroded by browsers that support CSS3.

 

Javascript

Now the website can be replaced without just a few scripts, and the responsibility for scripts is growing. MVC and MVVM, these fashionable modes are also available in script development. The emergence of the AMD specification RequireJs is to help us with modular development. Websites require more and more scripts, although CSS3 will replace some of the script functions.

Unit Testing

Unit testing is a good thing. PHP has PHPUnit and Javascript Has Jasmine. The quality of software must be guaranteed by these test points. When developing PHP, I must write one where I can use unit tests. The advantage of writing a unit test in PHP is to determine whether the function is correct in advance and verify the unknown. A large number of unit tests can ensure the software quality, so that the tester is convenient. I also write unit tests when developing scripts. Jasmine is a good thing and can help me test some small functions to ensure that JS can pass accurately. Another function of unit testing is to assign scenarios for testing. However, this workload is too heavy. I have no time to do this and often have to do it manually. In this way, each time I change a function, in most cases, you may make some mistakes. Sad ......

PHPUnit test screen:

For the Jasmine test screen:

Flowchart

I have developed and found that I have drawn a flowchart and then showed it to the testers for testing, which will increase the test efficiency. In many cases, the demand is constantly changing, and the prototype cannot be updated. The requirement can only be said orally. The words mentioned above will be forgotten, and a test point will not be considered. However, if there is a flowchart, the branches above are clearly written, which makes it easy for them to test. This flowchart can also be shown to your team members to understand the composition of your code. In the future, maintenance for others will save a lot of detours.

Server Development

I now use two languages for developing server code: PHP and C #. I do not have a deep understanding of these languages. Now I only use a small part of them. When I used PHP for the first time, his ease of use shocked me and found that it was very convenient to use PHP for script interaction. The explanatory language was easy to change and the editor was not as resource-consuming as VS2008. One of my former colleagues developed PHP and even used Notepad ++ directly.

Browser

I am used to using firefox as my default browser, firebug, and other plug-ins, which makes it easy for me to debug websites and plug-ins with that Evernote, it makes it easy for me to capture the content of the webpage to my notes.

Click the network to view the current loading status:

On the console, I often use console. log () to print and view ajax requests:

 

Development habits

Every day, developers record what time periods are being done. Develop your estimation capabilities in the future. I will save my Evernote for any questions I encounter, so that I can check them on any computer at any time.

Problems encountered during development

1. unclear requirements

This is often the case, which leads to frequent rework. Because it is not clear, I often consider how this logic should be implemented, slowing down the development speed. I can only decide what content to place on some pages.

2. the designers and engineers may have different understandings on the page.

The page designer designed a beautiful page, but the engineer said that this module is not available now. What should I use to fill in this position? This issue is often considered. There are also a lot of details on beautiful pages, which were not reflected by engineers when making CSS pages. Sometimes, designers only consider the page effect and ignore the association between pages, which makes engineers struggle to jump to the _ blank or current page during layout.

3. The problem detected by the tester is not an error.

The tester's understanding is different from the engineer's understanding. The problem may be different. They will propose a lot of bugs based on their needs and understanding. These may be improvements, it may be that the demand is not fixed yet. It may be that there is a conflict between the logic of the demand itself ...... these improvements can be organized to provide a memorandum of understanding for future website functions.

4. Communication errors with team members

Communication is a course of knowledge. When members exchange information, understanding errors may lead to various problems. Serious problems may affect the development goal. It is important to keep the information available during development.

5. browser compatibility debugging

The differences between different browsers are very big. It is impossible to achieve the same result. I can only achieve the same result in a rough way, and the effect is gradually enhanced. The most annoying issue is the compatibility of IE6, Which is unexpected.

6. Sometimes I take it for granted.

I saw a special effect on the Internet and thought it was awesome. Then I took it for granted to add it to a certain part of a project. It took time and effort, but the feedback and results were not satisfactory, sometimes it is even removed. I wrote a piece of code logic and thought it was very clever. But when it was actually used, this problem occurs, and some code was directly abolished. Sometimes, you still cannot be paranoid about your understanding. To be more rational, what suits the masses is a good thing.

7. Slow progress due to lack of relevant documents

For the development progress, some supporting materials such as simple database Relational Tables and simple business processes are often missing.