![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
I probably shouldn't have enjoyed today quite so much. It's not nice to laugh at someone else's misfortune, even if they have been an absolute back-stabbing S.O.B. towards you. It's petty, and it's immature... and I enjoyed every minute of it anyway.
My Group Lead (my immediate supervisor at work) decided, in his infinite wisdom, that rather than use an industry-standard version control system -- even though there are several available free of charge, including two that came with the OS they're using -- that he would just write one instead.
The thing hasn't worked properly since Day 1. It's so bad that if you want to back out a change, you then have to exit the program and restart, or else everything else you do will be screwed up.
Well, today the thing finally went kablooey. It destroyed its own database three times today, which he had to have restored from backup each time. By 4:00 this afternoon, he'd managed to restore it to the point where it could be used by one person at a time -- usually. Of course, the fact that people in 4 different bays, in 2 different wings of the building, are *required* to use this for *all* of their programs, makes it rather interesting to coordinate things so that only one person is using it at any given time....
And before you ask, no, I had *absolutely* nothing to do with it. To the best of my knowledge, it did this all on its own.
My Group Lead (my immediate supervisor at work) decided, in his infinite wisdom, that rather than use an industry-standard version control system -- even though there are several available free of charge, including two that came with the OS they're using -- that he would just write one instead.
The thing hasn't worked properly since Day 1. It's so bad that if you want to back out a change, you then have to exit the program and restart, or else everything else you do will be screwed up.
Well, today the thing finally went kablooey. It destroyed its own database three times today, which he had to have restored from backup each time. By 4:00 this afternoon, he'd managed to restore it to the point where it could be used by one person at a time -- usually. Of course, the fact that people in 4 different bays, in 2 different wings of the building, are *required* to use this for *all* of their programs, makes it rather interesting to coordinate things so that only one person is using it at any given time....
And before you ask, no, I had *absolutely* nothing to do with it. To the best of my knowledge, it did this all on its own.