Re: possible nomination for oracle wtf

From: joel garry <>
Date: Mon, 20 Jul 2009 09:50:20 -0700 (PDT)
Message-ID: <>

On Jul 19, 2:16†pm, ddf <> wrote:
> On Jul 19, 1:06†pm, John Hurley <> wrote:
> > On Jul 19, 8:23†am, wrote:
> > snip
> > > You shouldn't bash her, and even if you would like to bash her you
> > > should do that on her blog, not here. It exposes you as a coward.
> > Perhaps ... just perhaps ... this was already commented on at her
> > blog. †That would though require you to actually look and check on
> > what was said there ... instead of throwing around accusations.
> > Actually my posting was directed toward a system about to go live with
> > time bombs just waiting to potentially cause havoc. †I don't know who
> > the blogger is either professionally or personally except that they
> > are somehow an Oracle ACE.
> > I would have thought or perhaps wished that any Oracle ACE would have
> > been well aware of the dangers in exception handling with the when
> > others clause gets invoked. †It's not exactly a new concept here.
> Quoting from Chen Shapira's blog post you referenced:
> "We have this insanely complicated, highly visible, ultra high
> priority project going live this this Wednsday. The DBA who worked on
> this project nearly full time for the last 6 month left on 3 weeks
> vacation on Monday. Iím the replacement."
> So, she did NOT work on this system for six months, someone else did.
> She's an Oracle ACE, and I respect her knowledge and experience. †I
> also respect the fact she stepped into a situation for which she had
> no prior input and is reporting on the situation as it now stands.
> The problem is NOT with the Oracle ACE doing the reporting, it's with
> the prior DBA (on vacation) who allowed such a situation to exist.
> Funny you couldn't comprehend that.
> David Fitzjarrell

It seemed clear to me the problem wasn't with Chen or the previous DBA, but with a managerial system that hasn't defined DBA and developer roles in a coherent manner - who is responsible for coding standards here? This is the kind of thing often caused by MBA's thinking all IS personal are interchangeable cogs and underestimating the value and specificity of institutional knowledge. But of course, I'm necessarily just speculating. It could very well be the prior DBA didn't step up and tell developers not to do that, through wimpiness or arrogance - and/or it could be the developers were arrogant or untrained, unclear on all this "instrumentation" stuff. I just can't get past letting the DBA go on vacation just before implementation. That's the WTF.

I do think Chen is brave to publish this. Don't we all love horror stories?


-- is bogus.
"Users browsing this forum: Google Adsense [Bot] and 3 guests" - seen
on forum.
Received on Mon Jul 20 2009 - 11:50:20 CDT

Original text of this message