Re: career in SQL/Database administration

> (Anybody with suggestions on what to do with people like this please
> feel free to chime in.  :-D)

If you keep them involved in the development cycle, it's not usually a
problem.  A week of time isn't really enough.  You're not giving them a
chance to say "yes/no" that is/isn't what we want.  Get multiple projects
going at the same time, and give each of them a month or two.  That way,
you can design it and then give them time to review it and make
suggestions.  You can also give them a maximum number of divisions.  If we
tell the customer what kind of revisions can or can't be done, we're
pretty good.

If a client refuses to pay, that's a separate problem entirely.  It sucks,
but that's really a separate problem, don't you think?  We've had pretty
good luck with that, but we're in Oklahoma and if you screw someone over,
everyone hears about it.

Jon

>
> -Dan
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
>                http://www.postgresql.org/docs/faqs/FAQ.html
>