If that's what you got out of my posts, then you weren't paying attention. You might be absolutely right, but you're still going to be viewed as the thin-skinned dev who doesn't solve problems out of spite even though he can.thysm00 wrote:Thanks manSpitfire31 wrote:IMHO, there's too much moralising around here about the perceived attitude of the dev and not enough about the deplorable attitude of the OP.
/Joachim
I was about to answer with a long post, but that says it all
That's the entire point dude. Hundreds of people view this thread but don't reply, more just view the title. How many do you think read much more than the first post? You don't need to waste your breath trying to convince "me" of anything. Basically, this guy is exercising his "law of 250" and that is never a win for you.
He might have been rude, but you might have been a bit indifferent to his problems, we don't know, and it doesn't make you look good to share that kind of info here in an attempt to battle the customer. I know that seems unfair, but rude or not, he's still your customer and you still haven't solved his problem.
Sure, you probably do, but until you either replicate his bug, or test your solution on his system, you only think that you've solved the problem. Look, don't waste your breath here trying to convince me otherwise. I'm a software dev myself and I've seen this hundreds of times in my own work and other people's work. I can't count the number of times that devs thought that they knew what the problem was and thought they had the solution and it turned out to be something else. I know that you have a solution with high probability, but that probability isn't equal to one, even though you seemed to have convinced yourself that it is.and also that the problem was in fact identified, it's a bad note pairing, it being the merger of his keyboard of whatever else.
It could be a sure thing, all you have to do is swallow your pride, provide the customer with the solution and then you'll both know.