|
Agreed. I used to be the nice neighbor until MANY nights ruined by needy neighbors and I had to put my foot down.
Someone actually knocked on my "office" window at 3am, because they saw the light on. They needed to print their kids homework, and their printer was out of ink.
Can you imagine? Worse, the kid was in bed! I sent them to Kinkos, and let EVERYONE know that I had a friend who did all of this as a business, and would gladly come over and take care of anything they wanted for her normal rate, and a 1hr minimum charge. HIGHLY recommended.
Every time someone asked me anything (at a cookout, or the pool, I gave them her card), and explained I am not in that business. Once the 5 worse offenders realized I was NOT going to help them, it all stopped.
Even with that, I had one person call me confused "I called her, but she wants to charge me!"
(Yeah, kinda the point!)
One neighbor, in particular, went out of his way to repay the debt with a favor, and bought and delivered lava rock as a thank you. I only asked if he would go pick it up with me, so I could use his pickup truck for this dirty load. Once he knew my goal, he did it all by himself in the wee hours of the morning, and had the front yard done as I woke up! I offered to pay, and he laughed. He apologized that his home computer network was so bad that I spent 4 hours on it (and gave him an old switch to replace the bad one causing most of the issues)...
My doctor calls me about once every 3 months to ask "how do you turn on the file preview again?"
What I hate: He acts like he is calling to see if I am okay. He ALWAYS has a computer question!
|
|
|
|
|
TeamViewer is free for use as you describe. (personal non-commercial use) And they have a fairly simple means of getting things setup remotely on the remote side.
I would not leave it up, as I did and caught an intruder who managed to get around the security in place for TeamViewer ( older version no longer current) so today I use TeamViewer but do not leave it waiting for a connection unless there is a present need to get on the remote.
|
|
|
|
|
My boss just wont listen...
How can I convince him that our users are reporting FAKE BUGS?
... such stuff as dreams are made on
|
|
|
|
|
You just have to propose fake solutions 
Or... set the users that report fake bugs to null.
"I'm neither for nor against, on the contrary." John Middle
|
|
|
|
|
Kick him in the nuts.
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible."
- Mr.Prakash One Fine Saturday. 24/04/2004
|
|
|
|
|
Gotcha!
... such stuff as dreams are made on
|
|
|
|
|
Tell him the customers are experiencing REAL FEATURES.
|
|
|
|
|
If he believes in Trump tell him that Trump said the Bugs are Fake News.
If he doesn't believe in Trump tell him that Trump said the Bugs show the truth.
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
If you are not already using one get a good bug(issue) tracker.
When everything is closed as 'could not reproduce', 'misunderstood feature' or 'feature request, not bug' then your manager should get the message.
|
|
|
|
|
Had one of those (a manager) here - who didn't want the upgrade to be implemented because it would audit his activity (i.e., suspected vendor payoffs). He whined in sympathetic upper-management ears and they swallowed (hassle developers) until he finally got caught in a lie (so they finally spat).
It still took a while, but aforesaid employee was terminated.
Otherwise, we simply enjoy certain groups of users (really, their managers) stonewalling on final testing/acceptance. As I mentioned somewhere, before, they'll accept changes on their Home PC's/laptops/notepads/phones - and pay dearly for it - but when you actually make changes to make things better for them they balk.*
* I believe I still have to justifiable homicides left this quarter.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Logs?
I'm not sure where you're going with this...
|
|
|
|
|
Welcome to the Lounge. Please note for future reference that it may occasionally happen that people post jokes here.
... such stuff as dreams are made on
|
|
|
|
|
It's so hard to tell these days. 
|
|
|
|
|
megaadam wrote: How can I convince him that our users are reporting FAKE BUGS?
Reality is that is a management problem - not a technical one.
So there are two possibilities.
1. A customer is trying to play the system by attempting the invoke the acceptance criteria of the contract.
2. Most people are not malicious but some are. So some individuals will just do this for entertainment.
Solutions
1. For a customer that is attempting to play the system, then presumably the contract as a mediation clause and/or a termination clause. You (company) track the complaints and when they fall outside the bounds of acceptable boundaries invoke the contract. If the contract doesn't have either clause then of course the contract has a problem, a significant problem, and you should get a real lawyer to craft a real contract.
2. For individuals that are just screwing around then you track their posts and ban them after giving them some warnings. Obviously this requires that each user has their own login.
Both of the above should be something that a reasonable manager is should be aware of. And willing to take appropriate action when it is recognized.
Finally of course one must note that "fake" can mean many things. What it doesn't mean is "unable to replicate". So if you are judging that they are wrong, and there are multiple users especially with similar problems, are "fake" because you can't replicate it then the problem is with your determination of what the actual problem is. A reasonable manager, one with full cycle development experience, is going to be quite familiar with an inability to replicate. Bugs are still bugs if they cannot be replicated.
If the problem is replication then there are numerous mitigation strategies for that.
|
|
|
|
|
I recommend liberal use of the Wally Reflector.
|
|
|
|
|
Don't argue - it's job security for you. Just make FAKE FIXES for them all.
I'm retired. There's a nap for that...
- Harvey
|
|
|
|
|
Um, they don't do this. Be sure you have a good test account that acts exactly like a user account do your testing with that.
In nearly 30 years of programming, at 5 different firms, Web, Mainframe, SharePoint, .net, Jquery. I have yet to ever see any users report fake bugs. It usually is a case of me or my team not accurately testing the reports.
They aren't going to waste their own time reporting fake bugs.
To err is human to really mess up you need a computer
|
|
|
|
|
Capture the details, and either show him that it is NOT reproducible or "never" happens twice.
Don't try to make the customers look like they are lying.
Customers often look foolish on their own.
I had a lady do this on newly released software like 17 years ago. Complaining the software had so many bugs it was unusable, and was going to take down the business. But I noticed she did not report bugs on Monday or tuesday. She waited until the busiest day (wednesday) when everything was critical, and then ALWAYS had a problem. And it never added up to me. She ZAPPED all the data and did it by hand, stayed late, got paid overtime, and complained loudly.
It was rough. In the end, I suggested to the owner that her behavior felt like sabotage. That some of her own "it has to work this way" statements were a source of 1-2 of the real issues she did find.
(and because it was new, I gave her the benefit of the doubt for too long).
So, I asked the owner to do the work, and give her a week off. That he should know if the software was working. He found 1 TINY issue, found the software worked great, and was easy to use. He gave her another week off, and we tweaked the system some more.
Then he fired this lady when she finally admitted to sabotaging the whole thing. With the software he had, he was able to triple his business without hiring a new employee, and he has been a client ever since. In fact, I just did some work for him this week! We still laugh about this, because he trusted her so much, he was ready to fire me!
|
|
|
|
|
Gone, but remaining; it's powered down, but not fresh; it's missing altogether! (4, 3)
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
You should have gone off yesterday. You could have avoided doing today.
This space for rent
|
|
|
|
|
Yeah - I forgot I posted one this week already...
But if you are hinting you have it, you will have to spell it out! 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I'm not that daft. 
This space for rent
|
|
|
|
|
Left off ?
Gone = left and left over
not fresh = off
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
You are up on Monday!
The answer is right, the solution is "close enough":
Gone, LEFT
but remaining; LEFT
it's powered down, OFF
but not fresh; OFF
it's missing altogether! (4, 3)
LEFT OFF (as in "left off the list").
Loads of clues for you all!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Oops! Sorry - forgot to upvote your correct answer... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
