[missing-sync-winmobile-talk] Re: missing-sync-winmobile-talk Digest, Vol 39, Issue 12

[mick angel]

> Folks, get a grip!  Their communication has been crystal clear:
> Micro$loth changed the rules, pulled the rug out from under them,
> communicates between devices in a completely different way, and then
> doesn't document it adequately.  In fact, their own sync software,
> ActiveSync 4.1, doesn't even work well with Windoze.
>
> So, surprise, surprise, the MarkSpace folks are venturing out into
> uncharted waters, and cannot possibly tell you when Missing Sync will
> be ready--though I'm sure they'd like nothing better than to be able
> to.  I'll bet you money they're a lot more frustrated about it than
> you are, working hard on a product that brings in no money until they
> do finish it.  But you can rest assured they're making a maximum
> effort.
>
> Why is that so difficult to understand?
>
> [And no, I have no connection (get it? ;-) ) with MarkSpace except as
> a future first-time customer when they do release Missing Sync.]
> Cheers,
> --  
> Gib

Gib,

I don't think most of what you said is disputed: Microsoft changed  
the security scheme/protocols/rules/spec. It's a hard job starting  
from scratch. It's uncharted territory. They are doing the best they  
can. I'm sure they're coding as smartly and as quickly as they can  
and there are some very difficult problems to solve. I also (for now)  
think they will get there in the end.

What is not the same thing is the lack of communication to  
prospective customers. Once a coding job is underway (even in  
uncharted territory) you get a feel for how long it might take: a  
week? a month? six months? a year? Never? If a team worked for you  
and after two months of diligently working on a problem they *still*  
could not tell you *even very vaguely* how long it might take to  
finish, you'd start (rightly) getting worried.

To reiterate: I don't doubt that they are doing all they can to  
develop a working version. I *do* doubt they are being clever at  
managing expectations of their prospective and previous customers:  
It's one thing being frustrated at the coding problems, it's another  
to needlessly allow that frustration to pass to customers simply due  
to poor communication.

Mick.