Ok, TPTB at work decided to drop new training right away, so I was filling in some time (that I was not interested in doing real work during) with taking it.
It's the repeat of the workplace safety dreck, and diversity training.
So I got to watch a crappy slideshow of how to lift things, walk up stairs safely, and how to arrange by desk.
Then the diversity training.....
I'm all for diversity, and it's good that The Job at least follows the law in its efforts to hire/retain staff. But it serves nobody to have 45 minutes of videos where a person with a specific disability natters on about how it does and does not affect them on the job, and what others should do to when they do/do no need help. It really doesn't. Particularly when it is someone with a visible condition, where only the most idiotic of people still publicly offends with comments or actions.
Thursday, January 03, 2019
Wednesday, January 02, 2019
Still not getting through to that guy
This morning, returning to the salt mines, I noticed that one of our monitoring tools was showing an error condition that I knew was not strictly correct. When cow-orker arrives, we discuss, and determine that it's an artifact of the significantly different rates of monitoring and reporting of that metric.
So cow-orker and I decide it would be good to make it configurable, so that we can have it only report if it's consistently bad.
Cow-orker makes code change, tests in isolation, deploys to the one machine where the problem was manifesting.
Cut to an hour later, when second cow-orker reports that he is suddenly seeing malformed messages arriving at his client. We look, and the time coincides with cow-orker One deploying his changes. But he's off at an early lunch, so we put it aside.
After lunch, I pass One in the hall and mention it. He says that Two had mentioned it to him, but that they were seeing the errors from another machine, which had not been altered, so it could not possibly be his code.
So when I return to the pod, I ask Two, and he shows me the single, solitary error from another machine, and the ongoing several in a minute stream from the suspect machine. I show this to One, and he then looks and realizes he did not pull the repo before making his changes, so his binary reverted a week's worth of fixes. Off he goes to pull, re-implement, and redeploy.
Sheesh, you'd think that this 4th time he'd start to learn that at least he should at least just so "Ok, I'll check it out" before trying to dodge blame.
So cow-orker and I decide it would be good to make it configurable, so that we can have it only report if it's consistently bad.
Cow-orker makes code change, tests in isolation, deploys to the one machine where the problem was manifesting.
Cut to an hour later, when second cow-orker reports that he is suddenly seeing malformed messages arriving at his client. We look, and the time coincides with cow-orker One deploying his changes. But he's off at an early lunch, so we put it aside.
After lunch, I pass One in the hall and mention it. He says that Two had mentioned it to him, but that they were seeing the errors from another machine, which had not been altered, so it could not possibly be his code.
So when I return to the pod, I ask Two, and he shows me the single, solitary error from another machine, and the ongoing several in a minute stream from the suspect machine. I show this to One, and he then looks and realizes he did not pull the repo before making his changes, so his binary reverted a week's worth of fixes. Off he goes to pull, re-implement, and redeploy.
Sheesh, you'd think that this 4th time he'd start to learn that at least he should at least just so "Ok, I'll check it out" before trying to dodge blame.
Subscribe to:
Posts (Atom)