Do designers need to learn to write code? _ HTML/Xhtml _ webpage Creation

In general, after a webpage design is completed, the designer's ignorance is exposed and criticized. They leave the heavy work of creating web code to programmers. This phenomenon not only occurs in the network development industry, but also in the software and game development industry. The cruel fact is that the development progress may be stagnant by the designer. In pursuit of the best efficiency, designers are not only often criticized for their ignorance after completing a webpage design. They leave the heavy work of creating web code to programmers. This phenomenon not only occurs in the network development industry, but also in the software and game development industry.

The cruel fact is:The development progress may be stuck due to the designer.In order to pursue the best efficiency, designers not only need to draw, but also need to make it! In this article, I want to share with readers some reasons why designers need to learn to write code.

Practical Design

With a clear impression on how the final product will be implemented, designers will come up with more practical concepts. As an indispensable part of the development process, designers shoulder the burden of ensuring that their design can be smoothly transferred to the network medium, while also considering its availability, web page accessibility and reproducibility. A user-friendly website not only has simple and clear browsing sequence logic, but also provides users with all the information they need without being aggressive or messy. The only way to know whether a Web layout is feasible is to learn how to build a Web page.

Make communication easier

In almost all products with independent design and implementation, the design group and implementation group never meet the expectations of the other party, especially those intangible products, such as websites, software and games. This usually comes downProduct expectations and product feasibility compromiseAt present, it seems that this is difficult to perfectly unify. The solution is: designers should try to implement the design work to avoid confusion, misunderstanding, and false transfer in communication.

Convenient iterative development process

A Design in practice should not be absolute. I mean, the design should be flexible and friendly, so that it can be modified to cater to the technical limitations of the system without compromising its original meaning. These repetitive but necessary changes can only be implemented by the original designer. A designer/developer is more efficient than a developer who places the design in the designer's hands to make changes. And there is friction between the designer and the developer-in fact often.

Better and more harmonious results

I often like to think of software, network or game development as an orchestra, while the designer is a composer, and the developer is the conductor of the orchestra. Imagine what will happen if the two are the same person? The symphony will be amazing, charming, and pure! Not only is it the masterpiece of a master, but it is also personally directed by him!

Shorten development time

The role of a designer as a programmer means that the design and coding progress is continuous, even if not at the same time. The result is the shortening of the development cycle-who cares about efficiency?

More market-oriented designers

Modern designers need to improve their abilities to maintain their personal value. A set of skills is far from enough. We often need to wear different titles: designers, front-end developers, article authors, and project managers.

Implement your own design through learning, rather than making the design an orphan in the hands of developers-you have increased your value. After all, there is no harm in designing and coding skills mentioned in your resume. On the contrary, in this financial crisis era, enterprise restructuring (see large-scale downsizing) and spending reduction can also emphasize the importance of a person and avoid dismissal.

However, even if there are so many reasons to support designers to learn to write code, there is still an objection here.

A controversial article by referencing Lukas Mathis, "a designer is not a programmer "(Note 1)

If the designer implements his own design, he will be subject to two different goals: Code cleanliness and good user experience. These two goals are mutually contradictory. If you want to implement your own design, you will inevitably compromise the quality of the Code, which is not conducive to interactive design.

Designers who implement their own designs face two problems: they know that a great new idea will create chaotic code, and they also know that the existing code will be disrupted if the user experience is improved. The two are in conflict, because the user experience lies in small details, and these small details are ultimately ruined by their inability to confuse the code.

This appropriately summarizes the strong stance adopted by the Web developers and purification personnel. They are the conservative School and advocate to draw a line between design and development. Apparently,Designers create for humans and developers create for machines.Therefore, user experience designers should design the most feasible user interfaces and allow developers to make the most feasible programming decisions. Although there is some truth, when I study a user interface, my efforts to find inspiration from the code end with failure. In short, it is better to have a correct idea of technology and availability restrictions in mind.

Conclusion

In the final analysis, the scale of the development project may ultimately determine the roles of designers and developers. A small application can be composed of a Project Manager (Note 2)A large system requires different professionals!

Note 1Mathis-Lukas -- "Designers are not Programmers" -- ignore the code

Note 2Spolsky-Joel-describes a job called "designer and programmer"-"How to be a program manager"-Joel on Software

John Urban, a sophomore at the University of California, majored in computer science.

English original http://sixrevisions.com/web_design/why-designers-should-learn-how-to-code/