First, I agree entirely, "Just say NO" when a spec is doomed to failure, or is against your principles, or is just plain a bad thing (tm). I've worked mostly as a contractor and I have lost one or two bids by saying NO, but the bids that I got even when I did say NO were the best gigs I had - an employer who says "hmm, this guy has the guts to say NO, maybe he knows something I don't" is a good employer.
From the contractor's perspective, I've most often seen this combo - 1) the MIS department which takes the big picture only in so far as the entire goal is stability, lack of change, and lack of users bugging them 2) various web weenies who like making cool effects but have no concept of how what they do fits into any larger picture 3) the brilliant, innovative and humble contractor :-).
-
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.
|
