All this reminds me of the whole
discussion
on mappers versus packers (partucularly in Chapter 1).
It's difficult for non-software-development people to
understand the process of development -- to them, it
sometimes looks like we're just goofing off and if they
were just able to get us to apply ourselves we'd be that
much more productive.
One of the problems is that code isn't an easy
product to create metrics for. Sure, there's quantity, and
sure, there's output (does it do what it's supposed to?),
but I think non-development people always have the
suspicion that it could always do more and that it's the
lazy developer's fault it doesn't.
Chris
M-x auto-bs-mode
-
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.
|