The Cranky PM has been pretty happy at work lately. Thus, the drought of new cranky blog content.
So, you should all thank SugarSync for irritating the Cranky Product Manager enough that she shall now post.
Some background…SugarSync is a cloud backup service that the Cranky PM pays for. She uses it at home to keep her 3 computers backed up and in sync. Cool in concept, but not so cool in reality. A few months after subscribing, instead of just backing up her files, SugarSync decided to duplicate over 10,000 files – eating up all her hard disks and cloud storage. The Cranky PM then spent lots of time using 3rd party tools to remove the duplicates. The end result was a lot of lost time and at least a few lost files.
Irritating, to be sure. But the Cranky Product Manager is nothing if not forgiving of buggy newish products. It’s what SHE DOES, after all. So, reassured by the SugarSync Support that this was a one-off situation related to their latest upgrade, the Cranky Product Manager carried on and continued to use their service.
And then a month later it happened again. Argh! This time the Cranky Product Manager searched the SugarSync Forums for answers and found multiple threads related to this duplicate file issue. The most enlightening was this: http://sugarsync.hivelive.com/posts/c6fb6fb9db
This thread reminds the Cranky Product Manager about everything that is frustrating about dealing with a certain type of Code Boy:
1. Despite overwhelming evidence in its own forums that MANY customers experience this mass-duplication of files, the SugarSync CodeBoy(s?) (username “admin”) insists that this problem is a “corner case” and never really happens.
(We can tell that it is an actual code-slinging CodeBoy in the forum, because no self-respecting Customer Support Engineer would ever take this kind of attitude with a customer).
2. The SugarSync CodeBoy then pushes the burden of the bug onto the customer — insisting that they open support tickets, collect and mail in logs, etc…
3. The customer doesn’t send the logs in because:
* They are busy manually cleaning up the duplicate file mess and don’t have time to also help debug SugarSync’s software, and
* From the tone of the previous messages it is OBVIOUS to the customer that SugarSync does not recognize this as a genuine problem, and realizes it will be an uphill battle to convince SugarSync otherwise.
4. The SugarSync CodeBoy declares victory: “The customer won’t cooperate with me in reproducing this bug! I can’t do anything! So, this bug must not really exist!” Plus, I AM RIGHT! HAH!
Excuse the Cranky Product Manager while she strangles a voodoo doll that she created of this CodeBoy….
…OK, feeling better now.
Gotta say, it’s kinda rare to see this type of exchange played out in a public forum like this. Usually the Support people rightly prevent this type of unempathetic, obnoxious Code Boy from interacting with customers and others outside the company.
But within the company, who in Product Management has not encountered almost the exact same crap from a CodeBoy/Girl, at least once a release cycle? It is ABSOLUTELY MADDENING!
To have someone deny that a problem exists when MULTIPLE people have encountered it? To be told that the problem you are clearly experiencing is a “corner case” that doesn’t ever really happen? To be told its somehow your fault – some kind of user error situation? To have the Code Boys & Girls demand that YOU do THEIR effing jobs by spending ungodly amounts of time reproducing their damn bugs and verifying their alleged “fixes”?!?
AS IF product managers don’t have ENOUGH to do near release-end (market launch, get pricing proposed and approved, collateral & product training, and running beta programs, not to mention being neck-deep in planning the next release….the list goes on and on.), but now they have to be QA engineers as well?
All because some frigtard CodeBoy/Girl thinks it impossible that his/her code has bugs in it??!! Enough that s/he is completely denying the situation despite a preponderance of evidence?
BUT THEN, serendipitously, the Cranky Product Manager received a Truly Awesome article from a Code Boy who reads this blog. It’s about the process an Engineer goes through when faced with a thorny bug.
And now the Cranky Product Manager understands just a little bit better. She still wants to keep her voodoo doll collection of CodeBoys close at hand, but at least she’ll feel a bit more empathetic when sticking it with pins.
Read the guest post from Code Boy Extraordinaire in the next article (coming in a few minutes). It’s required reading for any product manager who has ever had a bug s/he reported marked as “not reproducible.”