Yes, the notion of usability engineer or architect has been lost
in the term 'web designer'. The back end web developer might think some
functionality is too cool, but if it's part of a useless
poorly designed interface, what's the point. We're building the
web site for our users not for ourselves, and the user interface
designers bring that focus back to a project.
The advantage is to have a well rounded web team - UID, tech,
content folks focusing on the project, not turf.
I'm a techie who has become less interested in the implementation
details and find the UID/design side of things more interesting
right now. Now I'm certainly no artist, so I always add graphic design
people to the team, too.
-
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.
|
