It wasn't anything usable...
-
Employee Number 1: "I was going to run that script you sent the customer on my system, but I can't find it. I did an SVN Update, but I didn't see it. What was it called?"
Employee Number 2: "It wasn't anything usable, so I didn't check it in."
-
@TwoScoopsOfHot said:
Employee Number 1: "I was going to run that script you sent the customer on my system, but I can't find it. I did an SVN Update, but I didn't see it. What was it called?"
Employee Number 2: "It wasn't anything usable, so I didn't check it in."
Not really a WTF, maybe it was very customer specific or wasn't that well-written that it was usable in general (but maybe it was for that one customer)
-
I've been in a silimar situation as employee number 2...
Employee Number 1: I ran that script you wrote for customer A on customer B's system, now everything's broken.
Sometimes it's better to not check in a one-off.
Employee Number 2: Why the hell did you do that?
Employee Number 1: Well, I don't know, I thought it would fix (completely unrelated problem).
Employee Number 2: Even though it was named fix_customer_a_only_do_not_use_elsewhere.sh?
Employee Number 1: Yeah, but I thought it would be OK....
-
Why don't you just ask him/her to check their email archives? They probably still have it...
-
sounds completely normal and not a WTF.
We sometimes have customers with specific problems. If we make a patch to see if it fixes there problems, we generally don't check it in. If it did fix there problem, then we either investigate more (is a general problem, etc) or just log the fault in case someone else reports a similar problem.