>>>I do it all the time, If you deliver poorly written code that is difficult to maintain, you're doing your customer a disservice and providing shoddy work. As a professional, I would expect to be paid to the job and for doing it right. The nature of software development is that you don't always get it right the first time. Sometimes I do get it right, sometimes not, because it takes time to fully understand the problem and the solution. Sometimes you don't fully understand it until you've gone the wrong path. My customer pays for me to learn about how to fix the problem and for the fix itself.
>>>
>>>>"When you get the code working, rewrite it so it looks like you knew what you were doing all along"
>>>>
>>>> then try billing the client for that.
>>
>>Yes but quite often a client will want function now and rewriting something that works adds zero functionality now. All this rewrite for correctness strikes me as ivory tower stuff.
>>
>>If you write crap at least comments help.
>
>
>>>All this rewrite for correctness strikes me as ivory tower stuff.
>
>One of our clients put it well when he said something like:
>"There's "budget" money and there's money that would otherwise pay for your kids' tuition and you'd better know the difference."
>
>Most of our clients are spending tuition money.
>I think that Craig is talking about spending budget money.
>I doubt that much tuition money would go toward esthetic rewrites.

Please don't mention tuition money ;-)