As convenient as it is to work by the hour, that's the genesis of the problem with lowering income by using modules.
It's more work upfront, but I think you should take a look at flat-rating. My preferred approach is something along the lines of "it will take X to dollars to make this, that and so-and-so headaches go away". It's to my benefit that I've invested the time into learning good toolsets. So as long as the customer gets what is good value *for them*, does it really matter how long it takes me to make the headache go away?
(Or, raise your rates. Take attorneys for example: They read documents, and fill in boilerplates for a living and don't blink at charging $200-$400 for their time. That's all due to prior investments in education and creating the boilerplates (a.k.a. modules.)
-
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.
|