bloody clients

[ramtops]

have one who found a problem last week - a real problem, and I fixed it, by adding a new page to the back office system.

she mailed back and said it still didn't work, but I put it down to web caching, proxies, browser, sunsports, etc.

this morning, she mailed again, and said it still didn't work. So I checked, and it worked fine. And then it occurred to me ...

yes, upon checking - she's using the *test* site to upload data to the *live* site.

clients - can't live with 'em, can't kill 'em.

Comments

[captainblue.livejournal.com]

I know what you mean: we have one - a friend too, which doesn't help - and frankly they're diverting too many resources away by the way they're opening up their (shared) mailserver to their clients.

They expect a premium service and are paying a budget price for it. I've already said if e-mail is enterprise-critical for them, they should maintain their own mailserver. Their own client webserver is available for them to operate a mailserver from. This would allow them to set their own access limits/tarpits, etc.

[landsmand.livejournal.com]

May I remind Madame of the following useful items:

a. The WDLY supplemental fee scale
b. Tactical use of the wheelbarrow in negotiating (or renegotiating) commercials

[ramtops.livejournal.com]

that's most kind, but Madame is always mindful of these things. This client is already on a WDLY uplift ...