|Employee retention policies
||[Aug. 18th, 2006|07:33 am]
See, here's the thing. |
I know, you're probably some hot-shit programmer.
I know your people probably aren't going to say "Well, not only were you an asshole, but you were wrong.
And I know that when your transaction log file estimates are off by an order of magnitude - that means by approximately a factor of ten, a decent programmer would probably know that, so I think I should inform you - it must be really, really embarrassing.
Especially when you think that a transaction log - which (among other things) keeps track of what needs to be inserted, where, and how far its actually *been* inserted, (yes, transaction log files can be pornographic-seeming during inserts) and holds the information necessary to return a database back to its starting condition - *only needs to hold the data that you're inserting and nothing else (like, you know, keeping track of what's been inserted, where, etc.). I mean, who would think something so stupid, when just thinking through what a transaction log *does* will provide you the answer?
And I know when we prod support people send you *all* the log files, say that it's *all* the log files, and say "there's an unexplained gap of six hours in the log files" it translates from plain English to programmer-asshole as "I deliberately chose not to send some of the log files you requested".
But if you really think that I'm not going to do my damnedest to make my job that much more pleasant by trying to humiliate you for your error at this point... well, you probably know me too well.
But someone is going to grovel - or at least make semi-congratulatory noises - if they expect that my job isn't going to consist much more of job-hunting rather than job-doing at this point.