Web Designers Learn some reasons to write code

Often, when a web design is completed, the ignorance of the designer can be blamed. They left the programmers with the heavy work of creating Web code. This phenomenon is not only found in the network development industry, but also in software and gaming development industries.

The brutal truth is that development progress may be stalled by designers. In order to pursue the best efficiency, the designer not only needs to depict the painting, but also needs to be able to make it! In this article, I want to share with readers some reasons why designers need to learn to write code.

Do realistic and workable design

With a clear impression of how the final product will be achieved, designers will come up with more practical concepts. As an integral part of the development process, designers are tasked with ensuring that their designs can be transferred smoothly to network media, while also considering their usability, readability and accessibility. A user-friendly web site not only has a concise, clear sequence of browsing logic, but also provides users with all the information they need without appearing aggressive or disorganized. The only way to find out if a Web layout works is to personally understand how to create a Web page.

Make communication easier

In almost all of the design and implementation of their own independent products, the design group and implementation team never meet the expectations of each other, especially those intangible products, such as Web sites, software and games. This is usually due to the product's expectations and product feasibility of mutual compromise, at present, it is difficult to perfect unity. The solution is: designers should try to design the work of the implementation, in order to avoid confusion in communication, misunderstanding and misinformation.

Easy Iterative development process

A design in practice should not be absolute. I mean, the design should be flexible and friendly and can be modified to meet the technical limitations of the system without distorting its original meaning. These repetitive but necessary changes can only be achieved by the original designer. A designer/developer can be more efficient than a developer putting a design in the hands of a designer to make changes. And there is friction between designers and developers-and, indeed, often.

Better and more harmonious results

I often like to think of software, web or game development as orchestral music, while designers are composers and developers are the conductor of the orchestra. Imagine what it would be like to be the same person? The symphony is going to be amazing, fascinating, pure! Not only is the master's God, but he himself commanded it!

Shorten development time

A designer's role as a programmer also means that the progress of design and coding is continuous, if not simultaneous. The result is a shortened development cycle-who cares less about efficiency?

More market-oriented designers

Modern designers need to improve their ability to maintain personal value, a set of skills is not enough, we often need to wear different titles: designers, front-end developers, article authors and project managers.

By learning to implement your own design, rather than making the design an orphan in the hands of the developer, you raise your value. After all, it's not bad to mention design and coding skills in a resume. On the contrary, in this financial crisis era of corporate restructuring (see: Mass layoffs) and spending cuts in the environment, but also can emphasize the importance of a person to avoid dismissal.

However, even if there are so many reasons to support the designer to learn to write code, there is still a dissenting voice.

A controversial article quoting Lukas Mathis "designer is not a programmer" (note 1)

If the designer realizes his design, he will be subject to two different goals: Clean code and a good user experience. These two goals are 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 creates confusing code, and they know that if you improve the user experience, the existing code will be disrupted. The two contradict each other, because the user experience is in small detail, and these small details are ultimately ruined by the fact that they don't have the heart to mess up the code.

This is an appropriate summary of the tough stance taken by the Web development purists. They are old school, advocating a draw-through between design and development. Obviously, designers create for humans, developers create for machines. Therefore, the user experience designer should design the most feasible user interface and let the developer make the most feasible programming decision. While this makes sense, when I look at a user interface, the effort to find inspiration from the code ends in failure. In short, it is better to have a correct idea of the technical and usability limitations in mind.

Written in the last

Ultimately, the size of the projects that you develop may ultimately determine the role of the designer and developer. A small application can be controlled by a project manager (note 2), while a large system will necessarily require different professionals!