The Perfect Trap

re: The Perfect Trap

K. Brian Kelley — Mon, 05 Mar 2012 18:31:35 GMT

Welcome to the light, my friend. ;-)

re: The Perfect Trap

Mike Adkins — Tue, 06 Mar 2012 19:02:19 GMT

Working for a "little" company in Jacksonville where I ran into you the first time, I admit this post irked me a bit; but only because it's mostly true. As a developer in an aggressive culture, I am constantly asked, hounded, beat with wet noodles, etc., as management constantly wants this-or-that change yesterday. If I don't get it done right away I don't get a raise. Meanwhile, I beg, plead, and bribe the DBAs to get something done, and I have to spend an hour in a meeting that they call where they explain why it can't or shouldn't be done. And then the devs take the heat for not getting it done. So I concur: "how hard can it be to tell developers 'No'?"

Pardon the rant. I'm done...

re: The Perfect Trap

RichB — Wed, 07 Mar 2012 11:32:10 GMT

@Mike...

Would you be the one spending the rest of the night and the next day fixing up the database after some kneejerk developer implemented something a little... incomplete?

Would you be the one who had to tell the CEO that you've lost 12 hours of customer data because a change went through that effectively serialised all the connections into a single open transaction that someone then rolled back.

Oh, and no he can't have his database back because the rollback will take another 10 hours or so, resulting in at least 24 hours effective downtime for a sloppy piece of error handling on a slightly weak piece of database design that just had to be done in a hurry?

If so, go ahead. Make the change.

<_<