Re: Declarative constraints in practical terms

David Cressey wrote:
> "Frank Hamersley" <terabitemightbe_at_bigpond.com> wrote in message
> news:4XBLf.15219$yK1.8064_at_news-server.bigpond.net.au...
<snip>
> If your primary role is prescribing process (in other words, programming)
> an imperative constraints may make more sense than declarative ones. I
> can't really speak to this. I programmed for twenty years before I got into
> databases, and I still know how to program. But I no longer look at the
> world through a programmer's eyes.
>
> In spite of Dawn's protestations to the contrary, I believe she still does
> look at the information through the eyes of a programmer, and not the eyes
> of a manager, or certainly not those of a data manager.

I'll buy the first and last phrases of that observation. I've doled out the designation of "DBA" before to someone on my team, but have never been a DBA and likely lack many of the skills and personality traits required.

> It shows up in
> every one of these discussions.

When I disagree with someone here, it makes sense that it is likely my process side showing since this ng leans heavily on the data side. I think that on any given project I would likely be viewed by the rest of the team as being more data-centric than process-centric. Maybe I'm just well-balanced. Nah, unlikely... --dawn Received on Sat Feb 25 2006 - 00:51:07 CET