2015 year-end rant! (Work again)
So, today. New Year's Eve, place is fairly dead, etc etc. I was a little annoyed yesterday because my boss made a big to-do about getting some wires out that night so they'll be done when we came in today, and she doesn't finish approving them until like, 5:30pm, which is QUITTING TIME, but you know what, that's just the way she is. But today was good. There was free breakfast, free coffee, and we get to leave early. I had really awesome leftovers ready for lunch, it's all roses.
We had a batch of payments to process for ACH, which as usual couldn't be done yesterday because they still haven't fixed the issue where we get the instruction verifications ahead of time, when they're actually useful, instead of at 4pm when we try to run the batch and all the banks are already closed because they're on the east coast or it's the holidays or they have a lot of people out. Just for shits and giggles as I was trying to explain the mismatch problem to AP, I notice that the NACHA file (that's the actual info that gets sent to the bank) in the preview link was a: not blank, b: not what was transmitted in the last batch. IT FUCKING HAD ONE OF THE DEVELOPER'S NAME IN IT, because it was a test file.
It was a test file in a PRODUCTION ENVIRONMENT. Where no test files are supposed to go, except that logic obviously didn't get passed down to our project management. And they had the gall to tell me that 'oh, I'm sure the operational controls you had in place would've prevented it from being transmitted'. Yes, that's like saying "Go play chicken with cars, you have insurance!"
And to add insult to injury, the PM I talked to WAS NOT SURPRISED. They KNEW there was a test file LIVE IN PRODUCTION and they didn't bother picking up the phone or shooting off a quick email to say "Hey, whazzup? Don't transmit anything, we've got a small problem, to be fixed in a jiffy." I was there until fucking 6pm last night when everyone had cleared out already, and they couldn't bother to stick their head up and see I was still there to let me know.
And then he sent an email to say the issue's fixed now, they've tested it. And that communication was completed between all involved business groups about the issue. I didn't respond because I didn't have a polite way of saying "FUCK YOU, YOU COMMUNICATED NOTHING." or "FUCK YOU, I DON'T TRUST YOU TO WIPE YOUR OWN ASS, I'll test the fix on Monday myself."
Because of this, my boss told me that we have to keep 'documenting' these issues, so we can present them 'quantitative evidence' that there are these problems and delays. Otherwise we'd just be the boy that cried wolf. As if I don't have enough things to do without dropping everything else whenever we have to make the payment and 'document' all of everyone else's fuckups.
And to close - we're definitely going to lose one person, another is considering another offer, and the third has a whole MONTH she plans to be off in 2016. Job hunting's sounding better and better.
Majo
We had a batch of payments to process for ACH, which as usual couldn't be done yesterday because they still haven't fixed the issue where we get the instruction verifications ahead of time, when they're actually useful, instead of at 4pm when we try to run the batch and all the banks are already closed because they're on the east coast or it's the holidays or they have a lot of people out. Just for shits and giggles as I was trying to explain the mismatch problem to AP, I notice that the NACHA file (that's the actual info that gets sent to the bank) in the preview link was a: not blank, b: not what was transmitted in the last batch. IT FUCKING HAD ONE OF THE DEVELOPER'S NAME IN IT, because it was a test file.
It was a test file in a PRODUCTION ENVIRONMENT. Where no test files are supposed to go, except that logic obviously didn't get passed down to our project management. And they had the gall to tell me that 'oh, I'm sure the operational controls you had in place would've prevented it from being transmitted'. Yes, that's like saying "Go play chicken with cars, you have insurance!"
And to add insult to injury, the PM I talked to WAS NOT SURPRISED. They KNEW there was a test file LIVE IN PRODUCTION and they didn't bother picking up the phone or shooting off a quick email to say "Hey, whazzup? Don't transmit anything, we've got a small problem, to be fixed in a jiffy." I was there until fucking 6pm last night when everyone had cleared out already, and they couldn't bother to stick their head up and see I was still there to let me know.
And then he sent an email to say the issue's fixed now, they've tested it. And that communication was completed between all involved business groups about the issue. I didn't respond because I didn't have a polite way of saying "FUCK YOU, YOU COMMUNICATED NOTHING." or "FUCK YOU, I DON'T TRUST YOU TO WIPE YOUR OWN ASS, I'll test the fix on Monday myself."
Because of this, my boss told me that we have to keep 'documenting' these issues, so we can present them 'quantitative evidence' that there are these problems and delays. Otherwise we'd just be the boy that cried wolf. As if I don't have enough things to do without dropping everything else whenever we have to make the payment and 'document' all of everyone else's fuckups.
And to close - we're definitely going to lose one person, another is considering another offer, and the third has a whole MONTH she plans to be off in 2016. Job hunting's sounding better and better.
Majo