Usually, after completing a piece of web design, the designer’s ignorance will be exposed and he will be criticized. They leave the hard work of creating web page code to programmers. This phenomenon is not only seen in the web development industry, but also in the software and game development industry.
The harsh truth is: Development progress can be stalled by designers. In order to pursue optimal efficiency, designers not only need to draw, but also need to be able to make it! In this article, I want to share with readers some of the reasons why designers need to learn to code.
With a clear impression of how the final product will be realized, the designer will come up with more practical and workable concepts. As an integral part of the development process, designers are responsible for ensuring that their designs can be transferred smoothly to the online medium, while also considering usability, web readability and implementability. A user-friendly website not only has a concise and clear browsing sequence logic, but also provides users with all the information they need without appearing overwhelming or cluttered. The only way to know if a web layout is possible is to learn how to build a web page yourself.
In almost all products that are designed and implemented independently, the design team and implementation team never meet each other's expectations, especially those intangible products such as websites, software, and games. This usually comes down to a compromise between product expectations and product feasibility , which currently seems difficult to perfectly unify. The solution is: designers should personally try to realize the design work to avoid confusion, misunderstanding and miscommunication in communication.
A practical design should not be absolute. What I mean is that the design should be flexible and user-friendly, capable of being modified to suit the technical constraints of the system without distorting its original content. These repetitive but necessary changes can only be implemented by the original designer. A designer/developer can be more efficient than a developer bringing the design back to the designer to make changes. And friction can arise between designers and developers - as is often the case -.
I often like to think of software, web or game development as an orchestra, with designers being the composer and developers being the conductors of the orchestra. What would happen if they were the same person? The symphony will be stunning, captivating, and pure! Not only is it the masterpiece of the master, but it was also directed by him himself!
Designersimultaneously filling the role of Programmer means that the progress of design and coding is continuous if not simultaneous. The result is shorter development cycles - who doesn't care about efficiency?
ModernDesigners need to improve their abilities to maintain personal value. Having a set of skills is far from enough. We often need to wear different titles: Designer, Front-endDevelopers, article authors and project managers.
By learning to implement your own designs, rather than leaving them orphaned in the hands of developers - you increase your own value. After all, it never hurts to mention design and coding skills on your resume. Conversely, in this era of financial crisis corporate restructuring (see: mass layoffs) and retrenchment, it is also possible to emphasize one's importance and avoid being fired.
However, even though there are so many reasons for designers to learn to code, there are still objections.
Quoting a controversial article by Lukas Mathis "Designers are not Programmers" (Note 1)
If a designer implements his own design, he is bound by 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 for the quality of the code, which is not conducive to interaction design.
Designers who implement their own designs face two problems: they know that a great new idea will create messy code, and they also know that if they improve the user experience, the existing code will be broken. chaos. These two contradict each other because user experience is all about small details, and these small details are ultimately ruined by their unwillingness to clutter their code.
This aptly sums up the strong stance taken by the “web development purifiers”. They are old school and advocate drawing a clear line between design and development. Obviously, designers create for humans and developers create for machines. Therefore, UX designers should design the most feasible user interface and allow developers to make the most feasible programming decisions. While there is some truth to this, when I was working on a user interface, my efforts to find inspiration in the code ended in failure. In short, it is better to have a correct idea of the technical and usability limitations in your mind.
Ultimately, the scale of the project being developed may ultimately determine the role of the designer and developer. A small application can be controlled by a project manager (Note 2) , but a large system will definitely require different professionals!
Note 1 Mathis-Lukas——“Designers are not Programmers”——ignore the code
Note 2 Spolsky-Joel - describes a position called "designer and programmer" - "How to be a program manager" - Joel on Software
The author John Urban is a sophomore at the University of California, majoring in computer science.
English original text http://sixrevisions.com/web_design/why-designers-should-learn-how-to-code/
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
