The best test of the future project for a Web Developer: show thumbnails of the site, consult, take note of all comments on the work of the project (not necessarily all of them embody a life), still useful to compare with other sites on the Internet. Same with the design. Typical error of Russian web designers without a lot of experience – forget the fact that the appearance of web pages is not only a work of art (and demonstration of the degree of ownership of Photoshop), but the interface and project officials to work with the site. Speaking candidly Ben Silbermann told us the story. In contrast, western web designers (Nielsen apologists) are doing ascetic web pages – sites where it is impossible to get confused and without extra code easy to work, but from an aesthetic point of view of design of such sites is as banal and unattractive. Find a middle ground – a problem the maximum at the stage of designing the site. The biggest problem with layout of the site – writing such a code, which would give the same or similar result as in all modern and legacy browsers on different operating systems to the site a little different on different monitors different resolutions and under different conditions (Disable or enable active scripting, style sheets, images, etc). In such circumstances, testing of the project is of particular importance. When writing code, tests are important in two cases: when writing code for "run-in 'it in conditions close to reality (at home or test server) and after placing the project on the production server.

Configuration files, environment variables, path to the site work modules and other nuances may be different on the test and the real servers. All these factors make a permanent testing site indispensable. For a professional web developer is much more important to program allows you to write code by hand, performing only routine and ancillary operations, such as AutoCorrect, highlighting the different components of the code in different colors, line numbering code convolution block site debugging scenarios, error messages, crashes work, etc. In this case, a web developer gets a lot more control over the end result of the project, because the program does not "solve" for him. Unlike the editors of "scratchpad type "from the visual, not only in that the main component of the program – is a text entry field, but also that they have no built-in interpreter code. The total of such programs – a focus on working with code and Web components, whether it be html tags or visually map the buttons to send the request, and the mass of auxiliary instruments – besides the previously mentioned syntax highlighting of code and different markup languages, writing code and debuggers – a means of working with ftp for the site to the server without the file manager, color palettes, tools to work with a set of pages as a separate project, etc. There are more differences. Visual and text-types – is baseline separation (although all visual editors let you edit the code manually, but there are text editors with rudimentary means of visual editing). The remaining differences are rooted in a set of functions programs.