Actually, he addresses the topic in detail, starting with not letting your developers draw icons that all end up looking like squashed bugs. He spends time on how to come up with icons to describe etherial concepts and how to avoid the dependance on icons to identify functionality.
Icons should be like short-cuts. They are an easily identifiable trigger for a piece of functionality, assuming that you know what it means. There should be text along with the icon to create that mapping in the users brain.

-pete
Entropy is not what is used to be.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.