Laceration Face
Actually my face is much better now. At least it doesn't hurt me anymore. I got the stitches out last Friday and there is not much of a scab left. I would post a picture, but most of you already know what my handsome face looks like already. If not, see the picture I used for this post.
In other news, it is time for a short rant about work:
Every time I think we as an organization can't get any dumber I am amazed by a newer dumber rule to follow. Apparently us technicians are really stupid and can't be counted on to do our jobs right. So, not only are all network activities relegated to be done between the hours of 2000 - 0400 we now have to have our work previewed by our management team. Even though they don't have a clue how to do the job. Because of that, we have to include all the gory details of what we are going to do during our outage. If this were being reviewed by someone technical then we could probably get away with less detail beause the person would understand what we are doing. So, in keeping with the "Lean" concept that this company touts constantly, here is our process for requesting an outage or work-in-area:
When we first submit a design to our review board we have to include a "Pre-SNAP" form (SNAP is the acronym for outage request, although I have no clue what it stands for) in order to get approved. We then have to take that form and put it in a folder that management reviews once a week to get approved. Then we submit it to what is called the "Triage Team" to get approved. In turn this is passed to our outage coordinators to get approved. So, to sum it up. This form has to be approved 4 times before we can do our work. Then, if we manage to make it past the gauntlet we have to have at least 2 people to do the job.
While no one wants to cause a network outage, stuff happens. And as long as the same person is not making the same mistakes (or we are not constantly bringing the network down) then I don't see the problem. This is a typical "knee-jerk" reaction to an unplanned outage that happened a couple of weeks ago. The network has a high availability rate. In the past when we have been "base-lined" against other IT companies we constantly are in the top 15 percentile, so I would say that we are not doing too bad of a job. Right now most of us are afraid to do anything on the network for fear of making a mistake.
OK, so this was a little longer rant than I had intended and probably doesn't make much sense to anyone outside of work, but I feel better now.
In other news, it is time for a short rant about work:
Every time I think we as an organization can't get any dumber I am amazed by a newer dumber rule to follow. Apparently us technicians are really stupid and can't be counted on to do our jobs right. So, not only are all network activities relegated to be done between the hours of 2000 - 0400 we now have to have our work previewed by our management team. Even though they don't have a clue how to do the job. Because of that, we have to include all the gory details of what we are going to do during our outage. If this were being reviewed by someone technical then we could probably get away with less detail beause the person would understand what we are doing. So, in keeping with the "Lean" concept that this company touts constantly, here is our process for requesting an outage or work-in-area:
When we first submit a design to our review board we have to include a "Pre-SNAP" form (SNAP is the acronym for outage request, although I have no clue what it stands for) in order to get approved. We then have to take that form and put it in a folder that management reviews once a week to get approved. Then we submit it to what is called the "Triage Team" to get approved. In turn this is passed to our outage coordinators to get approved. So, to sum it up. This form has to be approved 4 times before we can do our work. Then, if we manage to make it past the gauntlet we have to have at least 2 people to do the job.
While no one wants to cause a network outage, stuff happens. And as long as the same person is not making the same mistakes (or we are not constantly bringing the network down) then I don't see the problem. This is a typical "knee-jerk" reaction to an unplanned outage that happened a couple of weeks ago. The network has a high availability rate. In the past when we have been "base-lined" against other IT companies we constantly are in the top 15 percentile, so I would say that we are not doing too bad of a job. Right now most of us are afraid to do anything on the network for fear of making a mistake.
OK, so this was a little longer rant than I had intended and probably doesn't make much sense to anyone outside of work, but I feel better now.