I like how you work! To be fair though, all of that quality and the other work of thinking is probably already included in the €|$300/hour rate.

The $300/hr rate is, to be honest, quite cheap when you don't charge all the time that went into meetings and preparing to write the code. It's probably more like $60/hr if you included all that. However, I don't need to account for my whereabouts the rest of the time, and I can just show a log of the code in progress if I'm ever asked about the time I bill. Of course when you actually sit down and begin to write something new, you begin actually thinking about modules and namespaces and consolidating functions and which things you can streamline, and so on... which is why it's fun. You may change your mind several times as you realize that all of this behavior should go into the parent class or something like that. [I have a special $150/hr rate I sometimes bill for "yak shaving" - clients appreciate it, actually.] But then it's just about painting something which you already have in your mind. I prefer to be paid for my painting, by the hour, rather than ever charging a project rate. I'm always concerned that my consulting is going to be mistaken for wasted time. I never want to be accused of wasting a client's time or overbilling; but they understand that when I sit down to write it, it will be done right the first and last time, and that it could not be done any faster or better than that.

Coding is not making a thing that appears to work. It's craftsmanship. It's quite difficult to convince a client that something which appears to work as a demo is not yet suitable or ready for production. It may take 20 more hours before it's actually ready to fly. Managing their expectations on that score is a major part of the work as well.