4 ms·
While some of that may be true, it feels ridiculous/inappropriate as a response. The customer doesn't want a disertation about programming/support practices. Th
by megous 8y ago
While some of that may be true, it feels ridiculous/inappropriate as a response. The customer doesn't want a disertation about programming/support practices. The customer wants something made cheaper.
That can be satisfied to a large degree. You can just as well tell the customer: "OK, I'll do the obvious chnage, if something else breaks, we'll fix it later. It seems likely all will be fine. Ok?"
Some customers will be ok with that. And you'll bill for 30mins or whatever and everyone's happy.
- chris11 8y ago> Some customers will be ok with that. I'm not sure I would fully trust that. The client probably won't be happy if bugs from poorly tested code keep coming up. And it sounds like the client might question the dev teams work, if they are currently questioning the team's estimates.
- megous 8y agoThey have to be ok with that before the fact. You just have to make sure they understand what it means.
- gnulinux 8y agoThis doesn't make sense. If you're selling a product, the quality of your product shouldn't be customized/determined by your customer. Your customer should pay you to get the product with the described quality. If you never test your code and do 4-8 our changes in 30mins, in a year your codebase will be write-only mess.
- megous 8y agoI'm not selling a product. I'm selling a service. And cost of that is determined by the service level. At the "I change it you test it" level, it can be pretty cheap and fast.