8 design mistakes that developers often make

Designers are complaining that developers don't respect web standards, and background developers are complaining about why you can't add a space. PM is complaining about why the project is always postponed because of seemingly simple problems ... How can you improve the efficiency of the backend developers working with designers and front-end development engineers? believe that many web sites or software development companies are getting to similar problems.

From the ued point of view, our vocation is to pursue the user experience. We should try our best to stick to what we should insist on. The white Jay once said that the user experience is not just a ued thing, but the whole development team and the whole company need to participate.

We can't just complain, we're going to understand developers. Again, we make efforts to get developers to understand us.

We try to make changes first. (Pony Chapeau)

Original address: 8 Web design mistakes which developers make

An excellent web site is a combination of excellent design and good code, and you often find that designers have to understand the code, and developers try to design for themselves. Developers spend their college lives and work with other developers, and I can say for sure that programmers aren't designers. Thankfully, we used to be able to judge whether the code is reusable or compliant with the correct OO methodology, but it's not critical to aesthetics. But now, a developer's most valuable asset is his keen understanding of design.

Now, as far as I know, programmers may never need any design knowledge (or that designers never need to know about programs). But the truth is that every programmer with a personal project, a small number of clients, or a management role needs to be designed. Even, I can say, it is obvious that the greatest advantage of a freelance worker is the ability to nurture potential clients to make them eager to understand the entire site's construction process. So while a person is learning to be a developer and needs to learn to design (at least try to do), here are 8 mistakes I've heard or made.

"I know what looks good (I have Photoshop ) "

This is one of the reasons for being a bad designer. What is more hopeless is that it was so lame that he thought he was good. Every good designer has a "design standard" for measuring the design that comes from a design that is often favored. You need to spend time looking at great designs such as THEFWA, Faveup, design is kinky, and my personal favorite behance network these sites. You may also know how to choose a design magazine, such as how or print (note that both are not American and may be more international). Just as good programmers like to see (or comment on) Other people's Code, good designers always look at the work of others, whether it's a site, a billboard, or a menu. Without a good "design standard", even a large number of Photoshop filters won't save you.

"repeatedly using blue and white"

Most programmers scoff at a designer who always spends a lot of time picking out the exact colors for the site. However, the color is more important than you think, and you can't change the site when it is built (at least, you have to spend a lot of effort at that time). Like many things, it is helpful to observe a good designer's color scheme, and one of the best sites for color schemes is colourlovers.

"I put everything in the center."

In most cases, it's natural to center a portion of a title, a banner, and a copy. But in general, it's very unprofessional to center the text on a page. Left alignment is an insurance practice, but often it is best to depend on the circumstances. Better yet, use the rulers and grids in Photoshop to accurately compute parts of your site. This does not mean that your design is like a lattice, but the eye can notice that the parts that should be lined up are not in this order (especially the text). Each pixel is important.

"Use a free font ... It looks good for me .

I had some time to think: (a) All the lines look the same (b) there is no font worth paying for. I have now abolished both, to continue to learn more about the font of knowledge, it is a complex and beautiful world. Frankly, if there's one area where I can become an expert, I want to be a font. You can build a great site with just a little color and a nice font (this is just the basis of any great design). Again, in the font to do better, you need to read more good site to cultivate your eyes.

"We can put more information in there."

A common argument between working with programmers and designers is the "use of space", where programmers want to place as much information as possible on the page's obvious location. The designer argues that it is impossible for the eye to bear so many things, and it is best to place only logos and banners in obvious locations. Try to find the best balance, need to know (a) cluttered websites may have no effect (b) leaving White is not designer slack (c) the part called "empty" is necessary to highlight other elements.

"I don't want to pay for the photos."

The pictures or photos of the cake can be destroyed by a reasonable site, while the great pictures can be simply handled to look good. With so many resources on the web, there's no reason to use bad pictures. For non-profit sites, you can view stock.xchng or Flickr. For a business site, there are many sites, such as istockphoto (but need to know about copyright, because you may see the same photos on other sites soon). Finally don't be scared to spend a lot of money on finding the perfect picture on a site like veer.

"I don't have to ask for advice."

Ask more than you do behind closed doors, and you'll be the biggest fan of your designers (though you're wearing rosy glasses). You need to ask the designer you know in order to get a candid evaluation. Unfortunately, I know that most of the people I ask are just praise, not criticism. So let your self-esteem roll aside and put on the "knowledge" of the hat. Because these people are designers and you're not. Then, after you get their feedback, respect them, trust them, and make some changes.

"No need to get too much detail"

Just like your regular code needs to be raised (though it still does), you have some of the past designs, but it's far from great. It's easy to think of a great design. "It doesn't look like much," but in fact, great design takes a lot of time (especially for beginners in design). But with these great designs, you just see the final product and don't know how many edits and revisions have been made during the designer's time. Even, you might be amazed at how different a split line would be for a design. When you put all the elements together, don't think the design is finished.

In short, great design (like great Code) takes time, patience and skill--and therefore deserves proper respect. Although as a programmer (or content editor or other Web employee), you may never need to design a whole site, but I have a feeling that, more or less, you have to do a little design. If possible, try not to make any of the above mistakes ...

(Translation of the wrong place, hope Enlighten, please understand)