Time for iterator tests again. I've settled on the nickname "ickerators" for them. Privately, I have names for them which are considerably less politically correct.
I do not find these tests nearly as educational as just a head game. I've run into questions in the past where the only correct answer was to place a case in a status which 90 percent of the reviewers could not place cases in. Only a supervisor could do that. This time, there are question asking if a test would approve and then they don't name what test the question refers to!
I learn a small amount from them but learn much more from newsletters. And would learn a hell of a lot more if the information was better organized and accessible.
I failed the first test. Have to take it again. Passed the second one. Had a headache by the end of the first one.
On top of that, the entire network crashed again today. This is after they replaced servers this past weekend. By process of elimination, the same problems have been happening during the slowest time of the year and on some of the slowest days of the week. So the problem is not bandwidth. The same problem has now occurred after the servers were replaced. So it's not the servers. However, the problems have been happening for many months on the same days of the week, worst every single Tue and Wed but sometimes into Thur. So, the problem is predictable. Yet is not being prevented. That means there has to be something else going on which is apart from bandwidth and server function.
Then I ran into the same issue of getting thrown into calls when my status should have prevented that. Problem with that is that I'm usually closing documentation on a previous case and the new call removes that case. Then I have to go back to the previous case after I finish the new call. It increases my risk of error and slows me down.
Pulled a few weeds tonight but not a lot. Both garbage cans in the back yard were full and I had to transfer the contents (mostly weeds) to the big can for pickup in the morning. Sprayed some weed killer outside the garden.
I need a night out. Think I'll check another place for karaoke tomorrow night.
I do not find these tests nearly as educational as just a head game. I've run into questions in the past where the only correct answer was to place a case in a status which 90 percent of the reviewers could not place cases in. Only a supervisor could do that. This time, there are question asking if a test would approve and then they don't name what test the question refers to!
I learn a small amount from them but learn much more from newsletters. And would learn a hell of a lot more if the information was better organized and accessible.
I failed the first test. Have to take it again. Passed the second one. Had a headache by the end of the first one.
On top of that, the entire network crashed again today. This is after they replaced servers this past weekend. By process of elimination, the same problems have been happening during the slowest time of the year and on some of the slowest days of the week. So the problem is not bandwidth. The same problem has now occurred after the servers were replaced. So it's not the servers. However, the problems have been happening for many months on the same days of the week, worst every single Tue and Wed but sometimes into Thur. So, the problem is predictable. Yet is not being prevented. That means there has to be something else going on which is apart from bandwidth and server function.
Then I ran into the same issue of getting thrown into calls when my status should have prevented that. Problem with that is that I'm usually closing documentation on a previous case and the new call removes that case. Then I have to go back to the previous case after I finish the new call. It increases my risk of error and slows me down.
Pulled a few weeds tonight but not a lot. Both garbage cans in the back yard were full and I had to transfer the contents (mostly weeds) to the big can for pickup in the morning. Sprayed some weed killer outside the garden.
I need a night out. Think I'll check another place for karaoke tomorrow night.
No comments:
Post a Comment