Re: Code Review Process
- From: rjamya <rjamya@xxxxxxxxx>
- To: Chris Taylor <christopherdtaylor1994@xxxxxxxxx>
- Date: Mon, 11 Feb 2013 08:18:08 -0500
Well,
I thik that is the development model we have here and it is so far proven
to work reliably. That way java folks concentrate on their part of the pie,
we do on our, in the end, it is one well done delicious pie that management
loves. In my previous company, there was a firewall between dba and app
team, as a policy we were not *allowed* to touch code. I did it anyway
because my business asked for it, but in this company it is completely
different.
We do java jokes all day here and java devs send us no-sql articles, but in
the end, we can make the product work when we work
(design/code/review/test/implement) together. At-least that is my
experience and personally I love that approach.
Raj
On Sun, Feb 10, 2013 at 7:31 PM, Chris Taylor <
christopherdtaylor1994@xxxxxxxxx> wrote:
> Sometimes I think DBAs try to own too much stuff. Could you imagine
> server folks cross checking shell scripts, code checking, performance
> review, design review for every script the DBAs write?
> At some point we have to trust/educate the devs and treat them like
> responsible adults in my mind.
> All this to only say I'm with David ;)
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
