Thursday, July 20, 2006
Jerry Springer of Databases
13:37 |
Posted by
Sean McCown |
Edit Post
I just started a new project with a new group of devs. I feel like Jerry Springer because they're just spoiled children. They half-ass everything they do, and then run to the boss when things don't get sorted out right away.
It's amazing to me that these people can even function in society. I spend my time settling petty disputes, and fixing things that should have been thought through to begin with.
They constantly overwrite each other's code and blame it on someone else. They never backup tables before making major changes. They never verify SQL statements before asking me to run them. And most of it's just ridiculous crap.
You would think that since they have to work in their own dev environment, that they would manage it the way they need to, but instead they do the DB equivalent of sleeping with their cousins, and cheating on their sisters with their moms.
Let's grow up a little bit and start acting like we know what we're doing people. If you know the statement isn't correct then don't send it anyway. If you know there's a possibility you'll need to roll back a change, then backup the table first.
Here's the code for you:
Select * into NEWtable from ORIGtable
you can get fancier if you like, but that basic statement will get you by. Of course, if you wanna actually backup the DB first, that would be even better. LiteSpeed has object-level recovery so you should be able to pull back individual tables and schema code.
Stop running around like children making half-ass changes. Learn from your mistakes. If it keeps coming back to bite you (and it does), then stop doing it. You'll find you'll start making your deadlines and even getting to bed on time.
It's amazing to me that these people can even function in society. I spend my time settling petty disputes, and fixing things that should have been thought through to begin with.
They constantly overwrite each other's code and blame it on someone else. They never backup tables before making major changes. They never verify SQL statements before asking me to run them. And most of it's just ridiculous crap.
You would think that since they have to work in their own dev environment, that they would manage it the way they need to, but instead they do the DB equivalent of sleeping with their cousins, and cheating on their sisters with their moms.
Let's grow up a little bit and start acting like we know what we're doing people. If you know the statement isn't correct then don't send it anyway. If you know there's a possibility you'll need to roll back a change, then backup the table first.
Here's the code for you:
Select * into NEWtable from ORIGtable
you can get fancier if you like, but that basic statement will get you by. Of course, if you wanna actually backup the DB first, that would be even better. LiteSpeed has object-level recovery so you should be able to pull back individual tables and schema code.
Stop running around like children making half-ass changes. Learn from your mistakes. If it keeps coming back to bite you (and it does), then stop doing it. You'll find you'll start making your deadlines and even getting to bed on time.
Subscribe to:
Post Comments (Atom)
About Me
- Sean McCown
- I am a Contributing Editor for InfoWorld Magazine, and a frequent contributor to SQLServerCentral.com as well as SSWUG.org. I live with my wife and 3 kids, and have practiced and taught Kenpo for 22yrs now.
Labels
Blogumulus by Roy Tanck and Amanda Fazani
0 comments:
Post a Comment