Why To Write Tests For Your Code

Post by gatlin » Mon, Aug 29, 2011, 11:16 PM UTC

d0m wrote: post #19

gatlin wrote: post #3

I am relatively new to HN and have _read about_ but not _seen_ an anti-testing mindset around here. I imagine this article will stir that debate if it exists. Can anyone tell me why they would not want to write tests? I have no biases here.

If you're paid per hour and your client want you to take the less possible time. It's stupid; I agree. You can try argue with him/her about the importance of it, but in the end, it's their money so it's their choice.

I am not a Randroid or very libertarian but I like Howard Roark's way of dealing with clients: you ask me to build X, and I will do it the best way I know how. If you want so damn much control over the how then you build it.

It irks me when clients tell me how I should do the thing they're paying me to do. It seems counterproductive and is insulting.

Post by d0m » Thu, Sep 01, 2011, 1:47 AM UTC

gatlin wrote: post #31

d0m wrote: post #19

Earlier quoted context omitted.

If you're paid per hour and your client want you to take the less possible time. It's stupid; I agree. You can try argue with him/her about the importance of it, but in the end, it's their money so it's their choice.

I am not a Randroid or very libertarian but I like Howard Roark's way of dealing with clients: you ask me to build X, and I will do it the best way I know how. If you want so damn much control over the how then you build it. It irks me when clients tell me how I should do the thing they're paying me to do. It seems counterproductive and is insulting.

Hmm, it's more.. I can do it in x hours the best way I know of; or I can do it in y hours by writing crappy code. So, at the end, if you tell your client that 10 hours is not enough to build a quality software but he still insist, well, it's his money.

It's a little bit like if you eat at a restaurant and you've got 20$. The cook could tell you there's something really good and way better at 50$.. but if you're happy with something less good at 15$, well, it's your body and your money. (I know that development is way different and in the long term tests will save money, but depending of the project, it's not always the case.)

Re: Why To Write Tests For Your Code

Re: Why To Write Tests For Your Code