To complement and counter this post, I find that soliciting input from the end user is invaluable. This should be done during the planning and design phase as well as after release, ideally. You'll get the same input as if you were using it yourself, but you don't have to go around actually using all the code you write.

I've found that some/many coders and companies try to predict what users want, instead of actually asking the users. While there's nothing wrong with coming up with your own good ideas, I'm sure there are always things that you wouldn't have thought of that a daily user of your product is just itching to tell you about. A valuable side-effect of asking your users what they want and then giving it to them is that you appear to actually care about them. (Whether you actually do or not is irrelevant.)

---

---

• 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.