Sent by Theresa Mesa on 20 April 2005 22:10
I've explained this all to the client every which way but
Sunday, but I have to keep explaining it. Everything that crops up needs to
be explained every which way but Sunday, and repeatedly.
Sigh...Just when I think we're done and she understands, she asks the same
question again. She's not stupid, and she has a good heart, so I'll just
leave it at that. I've received some very helpful ideas from some people
here. Thanks!
On 4/20/05 6:22 AM, "Ben Henick" [EMAIL-REMOVED]> wrote:
> I also think it's only fair that the process be disclosed in situations
> where it's not forbidden.
>
> "When I run into browser bugs and such, I often consider posting to a
> professional forum for insight on those problems as they apply to the
> projects I'm working on." When pressed, you can say that it'll save them
> money - if somebody else ate up {x} hours solving that problem and can
> pass the solution onto for free, that's time that won't be billed to the
> end client.
>
> A little more than a year ago I was working on some hairy css on
> subcontract; my client had met me through a list, so she knew I wouldn't
> mind in the end if my work in progress was posted for the world to see.
>
> ...Except that it was being developed in the folder I didn't want exposed
> to search engines. And she posted it. Hilarity ensued.
>
> It *is* easier, I suppose, to beg forgiveness than ask permission, but it
> never hurts to explain up-front what you're doing.
>
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
