Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <ol> <li><p><strong>Build on the shoulders of those who have gone before.</strong> To be a great developer, you have to know your stuff. In the same way, to be a good designer requires understanding of some basic foundational guidelines. Some of it may seem pretty simple and tedious, but understanding the proper principles of typography, color theory, grid systems and so on can help you a lot. A few resources to get you going are:</p> <ul> <li><a href="http://rads.stackoverflow.com/amzn/click/1592535879" rel="nofollow"><em>Universal Principles of Design</em></a></li> <li><a href="http://rads.stackoverflow.com/amzn/click/0881792063" rel="nofollow"><em>The Elements of Typographic Design</em></a> by <strong>Robert Bringhurst</strong></li> <li><a href="http://rads.stackoverflow.com/amzn/click/1568989695" rel="nofollow"><em>Thinking with Type</em></a> by <strong>Ellen Lupton</strong></li> <li><a href="http://rads.stackoverflow.com/amzn/click/1568984650" rel="nofollow"><em>Grid Systems: Principles of Organizing Type</em></a> by <strong>Kimberly Elam</strong></li> <li><a href="http://rads.stackoverflow.com/amzn/click/0465067107" rel="nofollow"><em>The Design of Everyday Things</em></a> by <strong>Donald Norman</strong></li> <li><a href="http://rads.stackoverflow.com/amzn/click/0321344758" rel="nofollow"><em>Don't Make Me Think: A Common Sense Approach to Web Usability</em></a> by <strong>Steve Krug</strong></li> <li><a href="http://rads.stackoverflow.com/amzn/click/1491945923" rel="nofollow"><em>Microinteractions: Designing with Details</em></a> by <strong>Dan Saffer</strong></li> </ul> <p>That list should generate it's own follow-on books / websites reading list for you.</p></li> <li><p><strong>Ask questions.</strong> Find some designers you really like and ask questions. Try to understand why they made the decisions they did. Most people are pretty willing to talk about their own work. Asking questions helps you to understand why designers use (or don't use) certain design principles in their work.</p></li> <li><p><strong>Actually design (and seek out constructive criticism.)</strong> Like anything you do in life, reading and learning can only take you so far. At some point, you have to start practicing. Find a small circle / community of more senior designers who can review your designers and give you some brutal, but constructive criticism. Your stuff will suck at first. Everyone's work does. Designers spend hours upon hours honing their talents and skills. Don't get discouraged by it. Just like anything you can gain mastery in, it takes time. Having people in your life who can give constructive feedback is a huge help.</p></li> </ol>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload